[Touch-packages] [Bug 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution
Another instruction which appears to have issues with memory operands and breakpoint on the instruction is vpmuludq. This time it didn't crash but I was looking at completely incorrect multiplication results compared to incoming values to the instruction. To me this indicates like vpmuludq read the memory operand from wrong address which happened to be a mapped address. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1850258 Title: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution Status in gdb package in Ubuntu: New Bug description: I noticed random looking SIGSEGV to application when trying to continue execution after first breakpoint. I now seem to have narrowed the issue to SIMD instruction with memory operand as first breakpoint location. I haven't managed to figure out why the SIGSEGV is delivered to the debugger application. It is important have first breakpoint exactly at a problematic instructions. If I first break on a different instruction then later breakpoints won't reproduce that crash I haven't tested if this is a hardware specific issue. I managed to write a simple test case which reproduces the crash if breakpoint is set. I attached the test.cc which includes compilation and testing instructions. test.cc is supposed to generate a simple main function like: Dump of assembler code for function main(): => 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0# 0x6020 0x4528 <+8>: vmovd %xmm0,%eax 0x452c <+12>: retq I set breakpoint with: b main Then either continue or stepping causes SIGSEGV to the debugged application. This was happening already with disco. I only now figured out enough details to make a simple test case which is worth a bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdb 8.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 29 09:44:52 2019 InstallationDate: Installed on 2037-12-25 (-6632 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdb UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution
A bit more debugging I see that signal comes from kernel (si_code=0x80)
but it claims null pointer reference. I don't understand how it could be
a null pointer I would need to have better understanding what
happens in gdb and kernel to trigger the SIGSEGV.
I found out also that workaround is to have breakpoint but disable it
after stopping on the problematic instruction. If breakpoint isn't
active then execution continues without issues. Only issues is that I
don't know full set of instructions which actually trigger this issue. I
have had issues with some other memory referencing VEX coded
instructions. But I also have examples of memory reference instructions
which don't trigger the bug.
I attached updated test2.cc which has now signal handling dumping
siginfo.
Reading symbols from ./test2...
(gdb) b main
Breakpoint 1 at 0x650: file test2.cc, line 41.
(gdb) r
Starting program: /home/coren/project/test2
Breakpoint 1, main () at test2.cc:41
41 asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) disassemble
Dump of assembler code for function main():
=> 0x4650 <+0>: vmovdqa 0x19d8(%rip),%xmm0#
0x6030
0x4658 <+8>: vmovd %xmm0,%eax
0x465c <+12>:retq
End of assembler dump.
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
main () at test2.cc:41
41 asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb)
Continuing.
sig: 11, ctx: 0x7fffd740
si_signo: 11, si_erron: 0, si_code: 128
si_addr: (nil), si_addr_lsb: 0, si_pid: 0, si_uid: 0
Breakpoint 1, main () at test2.cc:41
41 asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb)
Continuing.
Program received signal SIGSEGV, Segmentation fault.
main () at test2.cc:41
41 asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb)
Continuing.
sig: 11, ctx: 0x7fffd740
si_signo: 11, si_erron: 0, si_code: 128
si_addr: (nil), si_addr_lsb: 0, si_pid: 0, si_uid: 0
Breakpoint 1, main () at test2.cc:41
41 asm("\tvmovdqa %1, %0\n" : "=x" (bar) : "xm" (foo));
(gdb) dis 1
(gdb) c
Continuing.
[Inferior 1 (process 9091) exited with code 01]
** Attachment added: "test2.cc (A test case with signal handler returning)"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+attachment/5301182/+files/test2.cc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1850258
Title:
First breakpoint at AVX instruction with memory operand causes SIGSEGV
when tring to continue execution
Status in gdb package in Ubuntu:
New
Bug description:
I noticed random looking SIGSEGV to application when trying to
continue execution after first breakpoint. I now seem to have narrowed
the issue to SIMD instruction with memory operand as first breakpoint
location. I haven't managed to figure out why the SIGSEGV is delivered
to the debugger application.
It is important have first breakpoint exactly at a problematic
instructions. If I first break on a different instruction then later
breakpoints won't reproduce that crash
I haven't tested if this is a hardware specific issue.
I managed to write a simple test case which reproduces the crash if
breakpoint is set. I attached the test.cc which includes compilation
and testing instructions. test.cc is supposed to generate a simple
main function like:
Dump of assembler code for function main():
=> 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0#
0x6020
0x4528 <+8>: vmovd %xmm0,%eax
0x452c <+12>: retq
I set breakpoint with:
b main
Then either continue or stepping causes SIGSEGV to the debugged
application.
This was happening already with disco. I only now figured out enough
details to make a simple test case which is worth a bug report.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdb 8.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 29 09:44:52 2019
InstallationDate: Installed on 2037-12-25 (-6632 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: gdb
UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution
Actually it seems like it is more restricted towards a few instructions with memory operand. But if breakpoint is set to them at any point of execution they crash. That means also breakpoint before and single stepping to problematic breakpoint will crash application. But single stepping over problematic instruction without breakpoint doesn't crash. That was adding to my earlier confusion why application crashes looked so random. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1850258 Title: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution Status in gdb package in Ubuntu: New Bug description: I noticed random looking SIGSEGV to application when trying to continue execution after first breakpoint. I now seem to have narrowed the issue to SIMD instruction with memory operand as first breakpoint location. I haven't managed to figure out why the SIGSEGV is delivered to the debugger application. It is important have first breakpoint exactly at a problematic instructions. If I first break on a different instruction then later breakpoints won't reproduce that crash I haven't tested if this is a hardware specific issue. I managed to write a simple test case which reproduces the crash if breakpoint is set. I attached the test.cc which includes compilation and testing instructions. test.cc is supposed to generate a simple main function like: Dump of assembler code for function main(): => 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0# 0x6020 0x4528 <+8>: vmovd %xmm0,%eax 0x452c <+12>: retq I set breakpoint with: b main Then either continue or stepping causes SIGSEGV to the debugged application. This was happening already with disco. I only now figured out enough details to make a simple test case which is worth a bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdb 8.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 29 09:44:52 2019 InstallationDate: Installed on 2037-12-25 (-6632 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdb UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850258] [NEW] First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution
Public bug reported: I noticed random looking SIGSEGV to application when trying to continue execution after first breakpoint. I now seem to have narrowed the issue to SIMD instruction with memory operand as first breakpoint location. I haven't managed to figure out why the SIGSEGV is delivered to the debugger application. It is important have first breakpoint exactly at a problematic instructions. If I first break on a different instruction then later breakpoints won't reproduce that crash I haven't tested if this is a hardware specific issue. I managed to write a simple test case which reproduces the crash if breakpoint is set. I attached the test.cc which includes compilation and testing instructions. test.cc is supposed to generate a simple main function like: Dump of assembler code for function main(): => 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0# 0x6020 0x4528 <+8>: vmovd %xmm0,%eax 0x452c <+12>:retq I set breakpoint with: b main Then either continue or stepping causes SIGSEGV to the debugged application. This was happening already with disco. I only now figured out enough details to make a simple test case which is worth a bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdb 8.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 29 09:44:52 2019 InstallationDate: Installed on 2037-12-25 (-6632 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdb UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "A simple test case which crashes if first breakpoint is in main" https://bugs.launchpad.net/bugs/1850258/+attachment/5301095/+files/test.cc ** Description changed: I noticed random looking SIGSEGV to application when trying to continue execution after first breakpoint. I now seem to have narrowed the issue to SIMD instruction with memory operand as first breakpoint location. I haven't managed to figure out why the SIGSEGV is delivered to the debugger application. It is important have first breakpoint exactly at a problematic instructions. If I first break on a different instruction then later breakpoints won't reproduce that crash I haven't tested if this is a hardware specific issue. I managed to write a simple test case which reproduces the crash if breakpoint is set. I attached the test.cc which includes compilation and testing instructions. test.cc is supposed to generate a simple main function like: Dump of assembler code for function main(): => 0x4520 <+0>: vmovdqa 0x1af8(%rip),%xmm0# 0x6020 -0x4528 <+8>: vmovd %xmm0,%eax -0x452c <+12>: retq + 0x4528 <+8>: vmovd %xmm0,%eax + 0x452c <+12>: retq I set breakpoint with: b main Then either continue or stepping causes SIGSEGV to the debugged application. + + This was happening already with disco. I only now figured out enough + details to make a simple test case which is worth a bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdb 8.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 29 09:44:52 2019 InstallationDate: Installed on 2037-12-25 (-6632 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdb UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1850258 Title: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution Status in gdb package in Ubuntu: New Bug description: I noticed random looking SIGSEGV to application when trying to continue execution after first breakpoint. I now seem to have narrowed the issue to SIMD instruction with memory operand as first breakpoint location. I haven't managed to figure out why the SIGSEGV is delivered to the debugger application. It is important have first breakpoint exactly at a problematic instructions. If I first break on a different instruction then later breakpoints won't reproduce that crash I haven't tested if this is a hardware specific issue. I managed to write a simple test case which reproduces the crash if breakpoint is set. I attached the
[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
It appears there is a crash bug in the patch which needs a minor change:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=16800ea072dd0cdf14d951c4bb8d2808b3dfe53d
** Patch added: "Updated patch including the crash fix"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774168/+files/rebind-after-suspend.diff
** Patch removed: "Linked fix refreshed with quilt to apply cleanly"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774167/+files/rebind-after-suspend.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
New
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
I tested the linked patch. DNS queries work now after suspend and
resume.
** Patch added: "Linked fix refreshed with quilt to apply cleanly"
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774167/+files/rebind-after-suspend.diff
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
New
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
New
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639776] [NEW] dnsmasq fails to send queries out after suspend disconnects the interface
Public bug reported:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0,
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")},
16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I will
try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
** Affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
** Bug watch added: Debian Bug tracker #834722
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
New
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609546] Re: Slow DNS lookup through Netgear DG834G V4 router
I'm seeing a similar issue on current Ubuntu Yakkety with Android phone AP via WPA2-personal: $ systemd-resolve www.guugle.com www.guugle.com: 208.73.210.200 208.73.210.214 208.73.211.178 208.73.210.217 -- Information acquired via protocol DNS in 13.6889s. -- Data is authenticated: no `host www.guugle.com` and nslookup on the other hand return immediately during this time. Disabling DNSSEC and restarting systemd-resolved using the instructions above has no effect (the above trace is after disabling). syslog contains the lines: Oct 31 20:25:41 x systemd-resolved[5309]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.0.1. resolv.conf contains only `nameserver 127.0.0.1`. The problem disappears if I add also the line `nameserver 192.168.43.1` (that's the upstream DNS) --- however, the following line appears in the logs: Oct 31 20:34:05 x systemd-resolved[5309]: Using degraded feature set (UDP) for DNS server 192.168.43.1. -- 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/1609546 Title: Slow DNS lookup through Netgear DG834G V4 router Status in systemd package in Ubuntu: Triaged Bug description: On up to date Yakkety if I specify my Netgear router as the DNS server (via Network Manager) then DNS lookup takes about 30 seconds. I see the delay when I run, for example, systemd-resolve www.google.com or wget www.google.com I do not see the same delay if I run nslookup www.google.com A clue may be that in syslog I see Aug 3 21:20:56 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 127.0.1.1. Aug 3 21:21:16 dibbler systemd-resolved[2362]: Using degraded feature set (UDP+EDNS0) for DNS server 127.0.1.1. Aug 3 21:21:32 dibbler systemd-resolved[2362]: Using degraded feature set (UDP) for DNS server 127.0.1.1. I do not see the issue if I specify an external DNS server. I do not see the issue on 16.04, nor previous versions, or on other devices connected to the network. I have been using this router for years. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 3 21:24:07 2016 InstallationDate: Installed on 2016-08-02 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160802) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=aaca48e9-0f14-4b6b-ad60-fe93989c14b8 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068E1220491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068E1220491620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1609546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507062] Re: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection
Seems like network-manager 1.0.4-0ubuntu5.1 fixed this bug. That makes this like duplicate of LP: #1512749 -- 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/1507062 Title: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection Status in network-manager package in Ubuntu: New Bug description: This is regression from 10.04. It seems to reproduce often but not always which might point to some kind of race condition handled badly. Basic setup: * Huawei USB 3G modem * Network manager set to auto connect with saved pin * Laptop which has very few suspend-resume issues so I use suspending all the time I noticed the bug that modem led and network manager indicated that there was a connection. But connection didn't seems to work. My initial workaround in hurry was just to pull the modem from laptop and restart both modem manager and network manager. (they don't like modem unplugging or individual restarts but those are long standing separated bugs that I haven't cared to report) After restarting connection comes up working. I decided to investigate what is broken after resume and I could narrow issue to be that default route is missing from routing table. That resulted to very simple fix where I can simple manually add the missing default route. Broken table after suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Working table before suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default * 0.0.0.0 U 75000 ppp0 link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Command to add the missing route manually: sudo route add default netmask 0.0.0.0 metric 750 dev ppp0 That is at least so far only missing part of connection setup after suspend. I will report a separate bug if I see a different error causing similar reconnecting failure after suspend-resume. apport should include syslog with detailed log from suspend-resume and service restarts to get correct route tables. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 17 03:19:00 2015 InstallationDate: Installed on 2011-11-02 (1444 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IpRoute: default dev ppp0 scope link metric 750 169.254.0.0/16 dev ppp0 scope link metric 1000 176.93.96.110 dev ppp0 proto kernel scope link src 176.93.96.110 metric 750 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH ttyUSB0 gsm connected/org/freedesktop/NetworkManager/Devices/3 Dna dna internet 17b039cf-5b74-42af-af9a-d84c2519b250 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 ------ wlan0wifi unavailable /org/freedesktop/NetworkManager/Devices/2 ------ lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 ------ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507062] Re: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection
** Tags added: regression-release -- 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/1507062 Title: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection Status in network-manager package in Ubuntu: New Bug description: This is regression from 10.04. It seems to reproduce often but not always which might point to some kind of race condition handled badly. Basic setup: * Huawei USB 3G modem * Network manager set to auto connect with saved pin * Laptop which has very few suspend-resume issues so I use suspending all the time I noticed the bug that modem led and network manager indicated that there was a connection. But connection didn't seems to work. My initial workaround in hurry was just to pull the modem from laptop and restart both modem manager and network manager. (they don't like modem unplugging or individual restarts but those are long standing separated bugs that I haven't cared to report) After restarting connection comes up working. I decided to investigate what is broken after resume and I could narrow issue to be that default route is missing from routing table. That resulted to very simple fix where I can simple manually add the missing default route. Broken table after suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Working table before suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default * 0.0.0.0 U 75000 ppp0 link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Command to add the missing route manually: sudo route add default netmask 0.0.0.0 metric 750 dev ppp0 That is at least so far only missing part of connection setup after suspend. I will report a separate bug if I see a different error causing similar reconnecting failure after suspend-resume. apport should include syslog with detailed log from suspend-resume and service restarts to get correct route tables. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 17 03:19:00 2015 InstallationDate: Installed on 2011-11-02 (1444 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IpRoute: default dev ppp0 scope link metric 750 169.254.0.0/16 dev ppp0 scope link metric 1000 176.93.96.110 dev ppp0 proto kernel scope link src 176.93.96.110 metric 750 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH ttyUSB0 gsm connected/org/freedesktop/NetworkManager/Devices/3 Dna dna internet 17b039cf-5b74-42af-af9a-d84c2519b250 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 ------ wlan0wifi unavailable /org/freedesktop/NetworkManager/Devices/2 ------ lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 ------ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507062] Re: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection
Stupid me writing completely bogus. This modem wouldn't even work in 10.04. So obviously I tried to say regression was cause by upgraded from 15.05. -- 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/1507062 Title: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection Status in network-manager package in Ubuntu: New Bug description: This is regression from 10.04. It seems to reproduce often but not always which might point to some kind of race condition handled badly. Basic setup: * Huawei USB 3G modem * Network manager set to auto connect with saved pin * Laptop which has very few suspend-resume issues so I use suspending all the time I noticed the bug that modem led and network manager indicated that there was a connection. But connection didn't seems to work. My initial workaround in hurry was just to pull the modem from laptop and restart both modem manager and network manager. (they don't like modem unplugging or individual restarts but those are long standing separated bugs that I haven't cared to report) After restarting connection comes up working. I decided to investigate what is broken after resume and I could narrow issue to be that default route is missing from routing table. That resulted to very simple fix where I can simple manually add the missing default route. Broken table after suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Working table before suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default * 0.0.0.0 U 75000 ppp0 link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Command to add the missing route manually: sudo route add default netmask 0.0.0.0 metric 750 dev ppp0 That is at least so far only missing part of connection setup after suspend. I will report a separate bug if I see a different error causing similar reconnecting failure after suspend-resume. apport should include syslog with detailed log from suspend-resume and service restarts to get correct route tables. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 17 03:19:00 2015 InstallationDate: Installed on 2011-11-02 (1444 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IpRoute: default dev ppp0 scope link metric 750 169.254.0.0/16 dev ppp0 scope link metric 1000 176.93.96.110 dev ppp0 proto kernel scope link src 176.93.96.110 metric 750 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH ttyUSB0 gsm connected/org/freedesktop/NetworkManager/Devices/3 Dna dna internet 17b039cf-5b74-42af-af9a-d84c2519b250 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 ------ wlan0wifi unavailable /org/freedesktop/NetworkManager/Devices/2 ------ lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 ------ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1507062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507062] [NEW] After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection
Public bug reported: This is regression from 10.04. It seems to reproduce often but not always which might point to some kind of race condition handled badly. Basic setup: * Huawei USB 3G modem * Network manager set to auto connect with saved pin * Laptop which has very few suspend-resume issues so I use suspending all the time I noticed the bug that modem led and network manager indicated that there was a connection. But connection didn't seems to work. My initial workaround in hurry was just to pull the modem from laptop and restart both modem manager and network manager. (they don't like modem unplugging or individual restarts but those are long standing separated bugs that I haven't cared to report) After restarting connection comes up working. I decided to investigate what is broken after resume and I could narrow issue to be that default route is missing from routing table. That resulted to very simple fix where I can simple manually add the missing default route. Broken table after suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Working table before suspend: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default * 0.0.0.0 U 75000 ppp0 link-local * 255.255.0.0 U 1000 00 ppp0 rantapallo * 255.255.255.255 UH75000 ppp0 Command to add the missing route manually: sudo route add default netmask 0.0.0.0 metric 750 dev ppp0 That is at least so far only missing part of connection setup after suspend. I will report a separate bug if I see a different error causing similar reconnecting failure after suspend-resume. apport should include syslog with detailed log from suspend-resume and service restarts to get correct route tables. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 17 03:19:00 2015 InstallationDate: Installed on 2011-11-02 (1444 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) IpRoute: default dev ppp0 scope link metric 750 169.254.0.0/16 dev ppp0 scope link metric 1000 176.93.96.110 dev ppp0 proto kernel scope link src 176.93.96.110 metric 750 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH ttyUSB0 gsm connected/org/freedesktop/NetworkManager/Devices/3 Dna dna internet 17b039cf-5b74-42af-af9a-d84c2519b250 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- wlan0wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1507062 Title: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection Status in network-manager package in Ubuntu: New Bug description: This is regression from 10.04. It seems to reproduce often but not always which might point to some kind of race condition handled badly. Basic setup: * Huawei USB 3G modem * Network manager set to auto connect with saved pin * Laptop which has very few suspend-resume issues so I use suspending all the time I noticed the bug that modem led and network manager indicated that there was a connection. But connection didn't seems to work. My initial workaround in hurry was just to pull the modem from laptop and restart both modem manager and network manager. (they don't like
[Touch-packages] [Bug 1479310] [NEW] Card symbols in the monospace font are wider than single character should be
Public bug reported: Using font Ubuntu mono regular symbols ♣♦♥♠♧♢♡♤ are rendered about 1.5 times wider than monospace character wide is. That causes it to cover next character making it very hard to read. Those characters are U2660-U2667. Screenshot from gnome terminal showing the problem follows. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ttf-ubuntu-font-family 0.80-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 29 14:02:35 2015 Dependencies: InstallationDate: Installed on 2011-11-02 (1365 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to vivid on 2015-05-02 (87 days ago) ** Affects: ubuntu-font-family-sources (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Symbols overlapping next character in gnome terminal" https://bugs.launchpad.net/bugs/1479310/+attachment/4435713/+files/Screenshot%20from%202015-07-29%2014%3A10%3A54.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1479310 Title: Card symbols in the monospace font are wider than single character should be Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Using font Ubuntu mono regular symbols ♣♦♥♠♧♢♡♤ are rendered about 1.5 times wider than monospace character wide is. That causes it to cover next character making it very hard to read. Those characters are U2660-U2667. Screenshot from gnome terminal showing the problem follows. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ttf-ubuntu-font-family 0.80-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 29 14:02:35 2015 Dependencies: InstallationDate: Installed on 2011-11-02 (1365 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) PackageArchitecture: all SourcePackage: ubuntu-font-family-sources UpgradeStatus: Upgraded to vivid on 2015-05-02 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1479310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377220] Re: Google Chrome crash with mesa 10.3 on Intel GPU
Issue might be actually the X driver and mesa disagreeing how to handle the memory buffers. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 ** Bug watch added: Debian Bug tracker #757435 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757435 -- 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/1377220 Title: Google Chrome crash with mesa 10.3 on Intel GPU Status in Chromium Browser: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: When I start google-chrome on my Ubuntu 14.10 system the process it uses to test for a working GPU crashes and then Chrome falls back to software rendering. In chrome://gpu/ I get: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all [...] In Ubuntu 14.04 (and also previous versions), on the same laptop, the exact same Google Chrome used to work perfectly with GPU acceleration. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-dri 10.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting sensors limits [240G [234G[ OK ] * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: kwin CurrentDesktop: KDE Date: Fri Oct 3 17:48:09 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0494] MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 2 13:54:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1377220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
