Public bug reported:
The release of Ubuntu:
root@u2004:/home/user# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
The version of the package:
libgcc11:10.3.0-1ubuntu1~20.04 amd64
libgcc1:i386 1:10.3.0-1ubuntu1~20.04 i386
What you expected to happen:
I
@arges
dpkg --purge --force-all pciutils libpci3
git checkout -b test ef6c9ec3a45992d9e7ef4716d444252baf2013e1
make clean && make SHARED=yes install && \
make install-lib && reboot
It work without any problem.
After that I accidentally upgraded to 3.3.1-1.1ubuntu1.2 and now it
work, nothing
@sujithpandel,
I will try to bisect more as soon as possible.
Right now I can say only this:
pciutils/libpci3 git master (3.5.6) work
pciutils/libpci3 git tag/v3.3.1 work
pciutils/libpci3 3.3.1-1.1ubuntu1.1 work
pciutils/libpci3 3.3.1-1.1ubuntu1.2 does NOT work
--
You received this bug
Hi @sujithpandel,
tried with master branch of pciutils (3.5.6) and also with tags/v3.3.1:
In both case it work, I'm writing on my external monitor on DP-1-1 right
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First of all, I'm not opening a new bug because I'm on Mint 18.3 however
I think this is an Ubuntu bug anyway... right now I can't install
regular 16.04 Ubuntu, I will try as soon as possible.
With latest pciutils/libpci3 3.3.1-1.1ubuntu1.2 I cant see my external
display on DP-1-1 any more and
Public bug reported:
sibilla ~ # lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
sibilla ~ # apt-cache policy dpkg
dpkg:
Installato: 1.18.4ubuntu1.1
Candidato: 1.18.4ubuntu1.1
Tabella versione:
*** 1.18.4ubuntu1.1 500
500 http://it.archive.ubuntu.com/ubuntu
Sorry for the wrong status change, inadvertently set it to "Fix Committed".
I confirm this bug.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553503
Title:
multi monitors - black flashes or black screen when the mouse
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472968
Title:
acpi-cpufreq should be built as module and not built-in
To manage
Public bug reported:
acpi_cpufreq should be built always as module and NEVER builtin
because it prevent phc-linux being loaded, and also any other
acpi_cpufreq replacement provided by the vendor if any.
phc-linux is very important if you need to downvolt some cpu.
It's important, especially for
@Cyberbob, I'm in the same situation:
SSD 840 EVO and Linux Mint 17.1 Mate Edition...
*If you upgrade your 840 firmware you will need to **rebuild a custom*
*kernel with the proper ATA HORKAGE, as I do since the upgrade,*
*or you will need to use libata.force=noncq (**which I discourage)**.*
@Cyberbob, I'm in the same situation:
SSD 840 EVO and Linux Mint 17.1 Mate Edition...
If you upgrade your 840 firmware you will need to rebuild a custom
kernel with the proper ATA HORKAGE, as I do since the upgrade,
or you will need to use libata.force=noncq (which I discourage).
Don't know if
@chiluk:
Nothing wrong electrically and NO data loss, simply the new firmware is buggy.
With EXT0DB6Q errors are every time on different sectors.
With libata.force=noncq, or even better with a patched kernel
(ATA_HORKAGE_NO_NCQ_TRIM for the Samsung SSD 840 EVO) there is no error at
all, no data
Today it failed even in runlevel 1, the best solution seems to be
libata.force=noncq if you can't rebuild the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449005
Title:
trim does not work
I can't boot at all in runlevel 5 and I have a lot of FAILED COMMAND:
WRITE FPDMA QUEUE.
I can boot only in runlevel 1 and after echo 1
/sys/block/sda/device/queue_depth everything work properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have just done a fresh install of karmic alpha 4 and I must
say that in my previous post I missed the most important things:
While I confirm that for me it work only with video=radeonfb:1280x1024...@60
this is not enough, I must also install packages from xorg-edgers fresh X
crack...
here:
I have the same problem (using 2.6.31 kernel, 3d is not working using
radeon x1600 with the radeon driver) and I found a solution:
appending this to the kernel parameters fixes the problem:
radeon.modeset=1 video=radeonfb:1280x1024...@60
Now I have dri, all desktop effects enabled, a nice
Jim,
thanks for your reply!
I alredy use dd up to bs=1M, but never more than 1M...
I'm going to test it with 2.6.31 as soon as possible, but I can't do it
now because I need vmware at work (but this is another issue...).
--
elevator=cfq (default) cause starvation
I asked to remove comment 13 since it
is completely wrong, but it's still there.
As I saw BUG: unable to handle kernel paging... I start
thinking I can't understand what's happened, so I'll send
it and someone will read it...
Now, It was caused by umount and I can't understand why,
it was not an
Yesterday I was copying (really trying to copy)
78 GB of data from a disk to another one.
Source:
Caviar WD2000BB-22GUA0, a 200GB PATA disk.
USB2.0 to IDE adapter: EBL35U2
ext2 partition...
Dest:
my internal WDC WD3200BEVT-22ZCT0.
ext3 partition...
The system become slow as the copy start,
as
from http://bugs.kde.org/show_bug.cgi?id=196554
What's the Qt version? (run qmake -version in console to get it. or paste
here output of ldd `which kmines`)
and...@kubra:~$ qmake -version
Qmake version: 1.07a (Qt 3.3.8b)
Qmake is free software from Trolltech ASA.
and...@kubra:~$ qmake-qt4
Please note that the red and blue dot are a sign to highlight strange
squares, and are not present in kmines...
Just look the square's corner and see that it's different in some
case...
--
kmines show where mines are...
https://bugs.launchpad.net/bugs/387113
You received this bug notification
What described in 343371 was another problem and I had that one too...
I'm not too lucky...
I resolved it adding my hd (WDC WD3200BEVT-22ZCT0) in the NCQ blacklist
in drivers/ata/libata-core.c and now I can read very big files from the disk
without any problem...
However, the visible slowdown
echo 1 queue_depth was not enought in my case.
What you see in queue_type when you do that?
simple, none or something else?
I resolved it adding my hd (WDC WD3200BEVT-22ZCT0) in the NCQ blacklist
in drivers/ata/libata-core.c and now I can read very big files from the disk
without any problem...
Public bug reported:
Binary package hint: kmines
In the attached image you can see that some squares are different.
Some of that different squares are mines (see next image...).
Squares change in this way only after the first click and are normal
on a new board before starting playing...
** Attachment added: kmines1.png
http://launchpadlibrarian.net/27907960/kmines1.png
--
kmines show where mines are...
https://bugs.launchpad.net/bugs/387113
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: kmines2.png
http://launchpadlibrarian.net/27907964/kmines2.png
** Description changed:
Binary package hint: kmines
In the attached image you can see that some squares are different.
Some of that different squares are mines (see next image...).
Squares
take a look at bug 381300!
please boot with elevator=noop and try if the problem persist...
--
Very poor desktop response (high latency) during I/O-load with SATA+NCQ
https://bugs.launchpad.net/bugs/343371
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looking around I found this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/343371
He talk about reading big files, so I make some test and I found out that I
have this problem too, even with noop:
This time (just reading a big file from a sata disk, not using a pendrive) the
system
This is another test: this time I wrote a 6GB file on top af an ext3 fs
on top of a 8GB pendrive...
This 8GB pendrive is slightly faster than the other one...
-- noop --
elapsed: 10' 38, no slowdown, all good...
avg-cpu: %user %nice %system %iowait %steal
Again: this time I simultaneously wrote two 3GB files on top af an ext3
fs on top of a 8GB pendrive, ...
-- noop --
elapsed: 11' 52, high iowait but no system slowdown, it's quite good.
avg-cpu: %user %nice %system %iowait %steal %idle
8.01
Andy, yesterday when I was at home after your message
I tried to test every scheduler also recording a lot of stat
on memory and cpu usage...
Quite a waste of time, but it should be usefull...
Well, not only I got no problem with CFQ, but it also performed
better than other in almost every case,
On my notebook (fujitsu-siemens amilopro v3505):
writing large file on a pendrive:
-- noop --
elapsed: 19' 31
avg-cpu: %user %nice %system %iowait %steal %idle
4.770.00 14.39 49.160.00 35.82
no slowdown, all good...
** Description changed:
Binary package hint: linux-image
I had many performance problems using a usb pendrive:
writing large files cause a system slowdown sometimes unacceptable.
I performed several tests and in the end the culprit was found to
be the CFQ scheduler which is used
If you can't change the default please consider the
possibility of doing (automatically) something like this
with any pendrive or ssd disk:
echo noop /sys/block/sdX/queue/scheduler
No one here has this problem?
--
elevator=cfq (default) cause starvation
https://bugs.launchpad.net/bugs/381300
Have you tried any of the other schedulers other than noop
elevator=as work quite well in my case, don't know about
elevator=deadline but I can test it...
...noop is unlikely to be the correct choice for rotating media.
May be it's not the fastest choice, but it work and doesn't cause
I tested it in a lot of different scenarios and now I think it is
not related to writing a lot of data on slow devices but
just moving a lot of data...
Simply I think CFQ does not work well and must be replaced.
** Summary changed:
- elevator=cfq (default) cause starvation with very slow
I'm not the only one that prefer noop:
http://lkml.org/lkml/2008/8/26/116
Nor the only one that has problems:
http://lkml.org/lkml/2006/8/14/198
** Description changed:
Binary package hint: linux-image
I had many performance problems using a usb pendrive:
writing large files cause a
Public bug reported:
Binary package hint: linux-image
I had many performance problems using a usb pendrive:
writing large files cause a system slowdown sometimes unacceptable.
I performed several tests and in the end the culprit was found to
be the CFQ scheduler which is used by default since
** Description changed:
Binary package hint: linux-image
I had many performance problems using a usb pendrive:
writing large files cause a system slowdown sometimes unacceptable.
I performed several tests and in the end the culprit was found to
be the CFQ scheduler which is used
** Description changed:
Binary package hint: linux-image
I had many performance problems using a usb pendrive:
writing large files cause a system slowdown sometimes unacceptable.
I performed several tests and in the end the culprit was found to
be the CFQ scheduler which is used
please backport iptables 1.4.3 from karmic to jaunty, it will solve a
lot of problem!
iptables 1.4.1 is unusable!
--
iptables-restore v1.4.1.1: Symbolic name 0x10/0x3f is unknown
https://bugs.launchpad.net/bugs/336842
You received this bug notification because you are a member of Ubuntu
Bugs,
I reported this bug here too:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4509
** Bug watch added: ALSA Bug Tracker #4509
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4509
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this
I followed the istructions at
https://wiki.ubuntu.com/MozillaTeam/Bugs#Crashes and gdb showed this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7dba6d0 (LWP 7803)]
0xae101b73 in alsa_lib_resampler_process_int () from
I was wrong...
If this time I'm not wrong the bug should be assigned to alsa-plugins (source
of libasound2-plugins)
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm using ffmpeg rigth now, I will try with the ms codec...
** Attachment added: moon_props.png
http://launchpadlibrarian.net/26207154/moon_props.png
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this bug notification because you are a member of
This site is region-locked to Italians only, which makes verifying and
diagnosing it very difficult
I can setup a proxy for you if you can debug it...
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this bug notification because you are a member of
Now I'm testing it with the ms codec...
** Attachment added: moon_props1.png
http://launchpadlibrarian.net/26207270/moon_props1.png
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this bug notification because you are a member of Ubuntu
Bugs, which
it crash in the same way even with the ms codec.
OT
and I tainted one of my linux box... should I reinstall it from scratch? No,
I'm joking, but how to remove this codec?
removing .mozilla/plugins/moonlight/silverlight-media-pack-linux-x86-5-1.so is
enought?
/OT
--
firefox crash while using
Public bug reported:
In some case conqueror send the wrong user agent string in headers.
I'm in Kubuntu Jaunty upgraded at 2009/04/28.
r...@kubra:~# dpkg-query -s konqueror
Package: konqueror
Status: install ok installed
Priority: optional
Section:
it is similar to:
#198273 [konqueror-kde4-http][trivial] user agent not sent in headers
when switching to webkit
but I think it is NOT a duplicate.
--
konqueror send wrong user agent using webkit
https://bugs.launchpad.net/bugs/368554
You received this bug notification because you are a member
** Description changed:
In some case conqueror send the wrong user agent string in headers.
I'm in Kubuntu Jaunty upgraded at 2009/04/28.
r...@kubra:~# dpkg-query -s konqueror
Package: konqueror
Status: install ok installed
Priority: optional
Public bug reported:
Firefox crash while using moonlight to see a stream.
To reproduce this problem go there and wait:
http://www.rai.tv/dl/RaiTV/diretta.html?cid=ContentSet-37f0f5d4-af33-48df-9281-2d46214c1b5d
This is the log:
and...@kubra:~$ firefox
DownloaderRequest:
** Description changed:
Firefox crash while using moonlight to see a stream.
To reproduce this problem go there and wait:
http://www.rai.tv/dl/RaiTV/diretta.html?cid=ContentSet-37f0f5d4-af33-48df-9281-2d46214c1b5d
This is the log:
and...@kubra:~$ firefox
DownloaderRequest:
some time it may take an hour to crash, but it will crash...
--
firefox crash while using moonlight
https://bugs.launchpad.net/bugs/367279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
After a quite long uptime my ip address is changed from 192.168.1.100 to
- 192.168.1.101, but the network manager (plasma-widget-network-manager
- ???) still report the old ip address.
+ 192.168.1.101, but the network manager (plasma-widget-network-manager)
+ still
The easiest way to reproduce the problem is:
1. Obtain an address via DHCP (i don't know if the problem exists even with a
static address... may be)
2. Change the address manually with ifconfig...
3. Take a look at the network-manager widget and see the old address...
--
** Attachment added: bug_networkmanager1.png
http://launchpadlibrarian.net/25558651/bug_networkmanager1.png
--
knetworkmanager report wrong ip address
https://bugs.launchpad.net/bugs/362555
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
Public bug reported:
After a quite long uptime my ip address is changed, but the network
manager still report the old ip address.
** Affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: New
--
knetworkmanager report wrong ip address
** Attachment added: bug_networkmanager2.png
http://launchpadlibrarian.net/25558674/bug_networkmanager2.png
--
knetworkmanager report wrong ip address
https://bugs.launchpad.net/bugs/362555
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to
ops...
some info:
and...@sibilla:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION=Ubuntu 9.04
it's kubuntu, and it is fully upgraded at 16/04/2009.
--
knetworkmanager report wrong ip address
https://bugs.launchpad.net/bugs/362555
You
** Description changed:
After a quite long uptime my ip address is changed, but the network
- manager still report the old ip address.
+ manager (plasma-widget-network-manager ???) still report the old ip
+ address.
** Package changed: knetworkmanager (Ubuntu) = plasma-widget-network-
manager
and...@kubra:~$ apt-cache policy kolourpaint4
kolourpaint4:
Installed: 4:4.2.2-0ubuntu1
Candidate: 4:4.2.2-0ubuntu1
Version table:
*** 4:4.2.2-0ubuntu1 0
500 http://it.archive.ubuntu.com jaunty/main Packages
100 /var/lib/dpkg/status
and...@kubra:~$ kolourpaint
Starting
The direct link to reproduce the problem is:
http://woytekm.googlepages.com/linksyswag200g-eu
It continue reloading this address:
http://pagead2.googlesyndication.com/pagead/ads
This bug persist with latest konqueror (4:4.2.2-0ubuntu1)
--
Infinite reload of a page
Public bug reported:
I'm on kubuntu jaunty beta.
Konqueror with webkit in some case continue reloading a page in an
endless loop.
To reproduce this problem go to:
http://woytekm.googlepages.com/
Then click on Linux on Linksys WAG200G.
Package: webkitkde
Version: 0.1~svn090218-0ubuntu1
** Also affects: kdebase (Ubuntu)
Importance: Undecided
Status: New
** Also affects: kdeartwork (Ubuntu)
Importance: Undecided
Status: New
--
notifications visible through the screensaver
https://bugs.launchpad.net/bugs/339902
You received this bug notification because you
** Changed in: Ubuntu Jaunty
Sourcepackagename: kdeartwork = None
** Changed in: kdeartwork (Ubuntu Jaunty)
Sourcepackagename: None = kdeartwork
--
notifications visible through the screensaver
https://bugs.launchpad.net/bugs/339902
You received this bug notification because you are a member of
This time the notification area appear completely white!
Some time I can see the message, some time not, but
the real problem is: how can an app go through the screensaver?
Isn't it wrong?
Does my hardware conf help?
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
I changed the bug report to be non private because even if it will be
treated as a security issue it is nothing that can be used remotely to
cause damage, so hiding it is unuseful.
** Description changed:
Binary package hint: kscreensaver
I'm in Kubuntu Jaunty Alpha 5 fully updated at 09
Every type of notification...
Kopete incoming messages, file transfer status, battery status, and so
on...
Attached a foto (very bad foto, excuse me and my e51...) that show
what happen when the screen is locked (it is asking for the passsword)
and I remove the power adapter.
** Attachment
Public bug reported:
Binary package hint: iptables
iptables-restore cannot restore a dump created by iptables-save:
r...@kubra:~# ipkungfu
Checking integrity: .. PASSED
Checking MD5 Hash of config files: OK
Restoring /proc settings from cache:OK
Restoring iptables rules from
I missed an important detail:
I'm on jaunty, updated 5 minutes ago.
Current iptables version is 1.4.1.1.
r...@kubra:~# iptables --version
iptables v1.4.2
r...@kubra:~# ipkungfu
Checking integrity: .. PASSED
Checking MD5 Hash of config files: OK
Restoring /proc settings from cache:OK
grendelkhan, you can try replacing /usr/bin/touch with something like
this:
-
#!/bin/bash
printf $1
-
it should work...
Don't forget to restore the original touch after apt-get upgrade...
bye,
Andrea
--
kernel bug when installing clamav-freshclam
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/8314688/lspci-vvnn.log
--
kernel bug when installing clamav-freshclam
https://bugs.launchpad.net/bugs/124141
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Incomplete = Confirmed
--
kernel bug when installing clamav-freshclam
https://bugs.launchpad.net/bugs/124141
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I replaced /usr/bin/touch with self-made touch, and it work:
now clamav-freshclam install just fine (and it seems to work).
but the bug remain...
somebody know if it can be a bug related to touch and not to the kernel?
bye,
Andrea
--
kernel bug when installing clamav-freshclam
It seems to be solved with bios B0F, so
this is a bios/hardware related problem.
iwlwifi:
wmaster0 IEEE 802.11a Frequency:5.68 GHz
RTS thr:off Fragment thr=2346 B
wlan0 IEEE 802.11a ESSID:
Mode:Managed Frequency:5.68 GHz Access Point: Not-Associated
RTS
an hardware
or BIOS related problem however it should work...
- If someone can get the spec from Fujitsu Siemens I will
- be happy to write a patch or utility to do the job.
-
bye,
Andrea Bravetti
--
both iwlwifi and ipw3945 are unable to turn off rf_kill
https://bugs.launchpad.net/bugs/105420
to write a patch or utility to do the job.
bye,
Andrea Bravetti
** Affects: linux-source-2.6.20 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
both iwlwifi and ipw3945 are unable to turn off rf_kill
https://bugs.launchpad.net/bugs/105420
You received this bug notification because
In my case it seems to be a DMA related kernel BUG.
Both usb and sound are on DMA 11, and my laptop has 3 different usb
controller: only 1 (the one on DMA 11) is affected.
--
Sound from ES1978 Maestro 2E garbled when USB CD-ROM drive plugged in
https://launchpad.net/bugs/21057
--
ubuntu-bugs
I have exactly the same problem, but on a Fujitsu-Siemens AMILO Pro v2010:
Garbled sound when an usb device is attached.
But my audio card is a VIA VT823... AC97 (vendor 0x1106, device 0x3059) and the
USB controller a VIA VT82... (vendor 0x1106, device 0x3104).
If it help...
As soon as possible
81 matches
Mail list logo
