Hey! Anybody here?! :) It's simle bug, so please - fix it!
--
Progress bar stays on 0% even after the burning begins
https://bugs.launchpad.net/bugs/346489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
I have same problem on ASUS k52jr laptop.
I try install xubuntu 9.10 i386 and have no problem with network - all works
fine.
Under windows 7 all works fine too.
But under ubuntu 9.10 amd64 - not any wired connection aviable.
When I manualy setup /etc/network/interfaces and /etc/resolv.conf. After
ps. kernel linux 2.6.31-14-generic
--
unable to configure network connection using wired ipv4 manual method
https://bugs.launchpad.net/bugs/449529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
after update to kernel 2.6.31-19 problem was NOT solved
--
unable to configure network connection using wired ipv4 manual method
https://bugs.launchpad.net/bugs/449529
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Synaptick packet manager also gave me this error:
E: linux-restricted-modules-2.6.28-16-generic: subprocess post-installation
script returned error exit status 1
E: linux-restricted-modules-generic: dependency problems - leaving unconfigured
E: linux-generic: dependency problems - leaving unconfi
I am using a notebook; Acer Aspire 4741G, Intel i5-460M, 4Gb, Nvidia GT420M
Host OS. ubuntu 16.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801331
Title:
Disco Dingo installation stopped/
Public bug reported:
Disco Dingo daily build failed to install in Virtual Box.
Installation started alright, but stopped with an error message some time after
passed the location screen
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-1
32 bit
on my notebook 64 bit it looks like the flashplayer is still working
how can I get the flashplayer working again?? I do need it.
else I have to start looking to other browser with working flash.
ard
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 56.0+build6-0ubuntu0.1
Technology Co., Ltd.
> dmi.chassis.type: 3
> dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
> dmi.modalias: dmi:bvnAwardSoftwareInternational,
> Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:
> rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:
> cvnGigabyteTechnologyC
again.
thanks for the attention and assistance given.
ard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720955
Title:
FF56 block flahplayer
To manage notifications about this bug go to:
https
ias: dmi:bvnAwardSoftwareInternational,
> Inc.:bvrF14:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4P:pvr:
> rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4P:rvr:
> cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
> dmi.product.name: P55A-UD4P
> dmi.sys.vendor: Gigabyte Technology
e the flashplayer is still working
>
> how can I get the flashplayer working again?? I do need it.
> else I have to start looking to other browser with working flash.
>
> ard
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: firefox 56.0+
Public bug reported:
ard@komputor:~$ lsb_release -rd
Description:Ubuntu 11.10
Release:11.10
distribution upgrade (update-manager) failed with error "Could not
calculate the upgrade"
/var/log/dist-upgrade/apt.log
http://pastebin.com/qbYd44gB
/var/log/dist-upgrade/mai
i did
apt-get update; apt-get upgrade; apt-get dist-upgrade
and it went again without any errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988929
Title:
update-manager crashed while calculating
>> Deselect of SSL is not a solution of the problem.
It helps me to solve theproblem In pidgin 2.7.4 (ubuntu 10.10)
--
Can't login to ICQ or AIM servers "Received unexpected response from
http://api.oscar.aol.com/aim/startOSCARSession";
https://bugs.launchpad.net/bugs/506647
You received this bu
Does this fix the issue?
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h
=for-next/fixes&id=5a3ae7b314a2259b1188b22b392f5eba01e443ee
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
On Tue, 9 Apr 2019 at 16:30, dann frazier wrote:
>
> Yeah, no crash anymore - thanks Ard!
>
> ubuntu@d06-4:~$ echo function | sudo tee
> /sys/kernel/debug/tracing/current_tracer
> function
> [ 72.778123] ftrace: far branches to multiple entry points unsupported
>
On 14 June 2018 at 13:02, Brad Figg wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this bug with the
> results. If the problem is solved, change the tag 'verification-needed-
> bionic' to 'verification-done-bionic'. I
Thanks Dann.
I can HTTP boot that mini.iso fine on my rev 0.2 Developerbox.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
For the record, DT boot is equally affected, even though the fix
mentions ACPI _HIDs etc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692548
Title:
Marvell MacchiatoBin crashes in fintek_8250_prob
Previous kernels produced a crash like this one:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
console [ttyS0] disabled
Unable to handle kernel paging request at virtual address 7dfffee0004e
pgd = 1f2542365000
[7dfffee0004e] *pgd=00013745c003, *pud=00013745d003,
*pm
again, confirming: `sudo apt-get remove --purge dbus-user-session` and
reboot resolved it for me on Ubuntu 16.04. No side-effects. On reboot,
the Passwords>Login keyring was available, where before it wasn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
On an arm64 system (Cortex-A57 based AMD Overdrive), dumping a lot of
data to a gnome-terminal window crashes the gnome-terminal-server
process.
For instance, doing something like
$ hexdump -C /dev/urandom
will crash within a matter of seconds with the following backtrace
Public bug reported:
The following Debian issue exists in the Ubuntu package as well
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
It breaks gnome-terminal and xfce4-terminal on arm64 machines.
The issue is fixed upstream in 3.5.13, and the fix was backported to
Debian stretch as wel
Actually, it appears this issue is caused by a bug in libgnutls:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
** Bug watch added: Debian Bug tracker #867581
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
--
You received this bug notification because you are a member of
On 1 September 2017 at 14:10, Julian Andres Klode
wrote:
> Do we have a reproducible test case for an SRU?
>
Doesn't the debian bug report have one?
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1707172
>
> Title:
>
On 1 September 2017 at 14:32, Julian Andres Klode
wrote:
> Ah, https://gitlab.com/gnutls/gnutls/issues/204 has more details.
>
> ** Description changed:
>
> + [Impact]
> + AES256-GCM ciphertext is all zero on arm64 with hardware acceleration,
> breaking gnome-terminal and xfce4-terminal which use
On 2 September 2017 at 15:49, Julian Andres Klode
wrote:
> @ard Are released older than zesty affected as well? I don't have a
> machine to test this, I'm just uploading the fix for zesty and artful.
>
No, the issue appeared only after upgrading to Zesty.
--
You received th
On 2 September 2017 at 16:22, Julian Andres Klode
wrote:
> Thanks Ard.
>
> Fixes for both artful and zesty are uploaded now.
>
Great! Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Bug is fixed on zesty with package version 3.5.6-4ubuntu4.3
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707172
Ti
This may be related to issues we encountered with LTO. Could you use the
GCC49 profile instead? The only difference between GCC49 and GCC5 is
whether LTO is enabled, they can both be used with a GCC that is in fact
6.x
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
When Clang itself is built with GCC 5 or later, it may crash when
building for the aarch64 architecture if the following patch is not
applied
https://www.marc.info/?l=llvm-commits&m=142918476428427&w=4
This applies to wily only: vivid uses GCC 4.9, and xenial already has
the
Public bug reported:
EFISTUB zImages for ARM64 contain two sections, a dummy .reloc section
and a .text sections covering the entire payload.
When attempting to sign such a zImage, sbsign fails in the
image_find_regions() like so
Starting program: /home/ard/build/sbsigntool-0.6/src/sbsign --key
Hi Riku,
I am in touch with the OpenSSL maintainer who authored most of the
assembler code in OpenSSL (for all architectures).
ARMv8 versions will likely be done in collaboration with him, including
(NEON) accelerated versions of SHA and AES (as the crypto extensions on
v8 are optional). I will k
In fact, this still does not look correct: it should read
SIXTY_FOUR_BIT_LONG not SIXTY_FOUR_BIT (the latter is intended for Win64
style LLP64 model)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11021
dr@odroid:~$ export http_proxy=http://[fe80::9864:b6ff:fe00:3410%eth0]:3128/
dr@odroid:~$ curl -o gl.deb
http://deb.odroid.in/5422-s/pool/main/m/mali-x11/mali-x11_20170718-r17p0-20503ff-3_armhf.deb
% Total% Received % Xferd Average Speed TimeTime Time Current
I can confirm that this is still the case...
On an ubuntu 20.04:
```
ard@lenny:~$ TZ=US/Eastern date
Mon Mar 29 09:08:43 EDT 2021
ard@lenny:~$ TZ=America/New_York date
Mon Mar 29 09:08:47 EDT 2021
ard@lenny:~$ TZ=EDT date
Mon Mar 29 13:08:51 EDT 2021
ard@lenny:~$ TZ=EST date
Mon Mar 29 08:16:16
The bug prevents use of systems "blessed" with nvidia optimus.
It has been fixed however.
https://github.com/systemd/systemd/issues/6908
I hope the fix can be incorporated into bionic, because it would be sad to have
an LTS release that can not turn of the nvidia GPU without rebooting the system.
I force installed the armhf build of libnss-build for vivid on my trusty
install, and it basically works, except for the update-rc.d line in the
postinst, which contains incompatible syntax.
So:
https://launchpad.net/ubuntu/+archive/primary/+files/libnss-ldap_265-3ubuntu2_armhf.deb
works stable on
To make the package work on trusty, you have to change debian/rules:
override_dh_installinit:
dh_installinit -- start . stop 20 0 1 6 .
should be:
override_dh_installinit:
dh_installinit -- stop 20 0 1 6 .
as update-rc.d gets confused by the empty start.
--
You received this b
-gnueabihf/nss_ldap.so
-> nss_ldap.so.1
-rw-r--r-- 1 root root 55640 Jul 18 2012 /lib/arm-linux-gnueabihf/nss_ldap.so.1
lrwxrwxrwx 1 root root41 Jul 18 2012
/usr/lib/arm-linux-gnueabihf/libnss_ldap.so ->
/lib/arm-linux-gnueabihf/libnss_ldap.so.2
This is on debian jessie:
ard@odroid3:~$
Hi,
This could be a dup of #1022903, as it seems that nss itself is looking
for libnss_.so.2 instead of libnss_.so .
Hmm, yes,
ln -s nss_ldap.so /lib/arm-linux-gnueabihf/libnss_ldap.so.2
fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The problem is the same as in #387576
libnss-ldap doesn't recognize armhf as a debian glibc system.
There are a lot of kludges in there about glibc. Isn't it easier just to merge
debian libnss-ldap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
patch configure patch to recognize armhf as glibc.
** Patch added: "libnss-ldap-armhf.patch"
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1388960/+attachment/4252289/+files/libnss-ldap-armhf.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
The biggest problem with the packages is that the original source contains a
configure script.
And that the autoreconf.patch patches the configure script. Making obsolete the
fix-glibc-test-for-armel-gnueabi.patch patch.
I patched the autoreconf.patch with attached patch.
Now on to the next bug..
n you can ignore my patch, since my patch opened up another
segfault somewhere...
If you want me to test stuff on armhf, let me know, since this is
only an ubuntu build server.
Regards,
Ard van Breemen
--
.signature not found
--
You received this bug notification because you are a member of Ub
I got the same bug with Ubuntu 12.04: menu->applications->accessories -> crash.
Actually every place that listed applications: if you scrolled past gedit, e17
crashed.
I've worked around it by de-installing gedit and gedit-common. Now it doesn't
crash.
If I am correct it was a bad list handling
Hmmm,
I also had to mv /usr/share/applications/xdiagnose.desktop out of the way.
I am not really sure what triggers it.
If I put that file in ~/.local/share/applications/
and then try to add that to my favorites, it crashes again.
It's not the .svg file, since I made a launcher with that icon.
--
Sorry for this spamming.
It definitely is the .svg despite my earlier statements. I think if you select
an icon by svg it gets cached. If you put a desktop file with
/usr/share/xdiagnose/icons/microscope.svg as the icon, and then try to add that
one, it will crash.
Using /usr/share/unity/5/lens-
Actually I can't use it, because the e17 PPA doesn't build for arm... I
have to build it myself.
But updates to 13.04 seems to have resolved this.
I will check this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
50 matches
Mail list logo
