Not sure how the truncate tool works internally, but it does the same
with the -s parameter.
$ truncate -s 48T size-test
truncate: failed to truncate 'size-test' at 52776558133248 bytes: File too large
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well ... the tool could print all possible reasons of the failure to
avoid confusion. Writing one byte at the last position seems to me a
good solution. If that's acceptable, it would really improve the user
experience. Thank you.
--
You received this bug notification because you are a member of
Oh, sorry, I thought the limit cannot be reached that easy in case of
sparse files full of unalocated blocks. Apparently the limit includes
the unallocated space.
I retested that again and the sparse file really gets truncated to 16TB
and I believe that's exactly the moment when the tool should
Public bug reported:
It seems e2image is unable to work correctly with large filesystems. I
get the following error with etx4 on top of 48TB RAID5 array.
# e2image -pr /dev/md3 md3.e2i
e2image 1.46.5 (30-Dec-2021)
Scanning inodes...
Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at
Public bug reported:
I was curious how e4defrag works and how it could optimize a speed and
loudness of 48TB mdraid array with four 16TB drives in RAID5 and tried
the defrag on the whole mountpoint. After a couple of minutes the
mountpoint became inaccessible and I found two of the drives marked
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905080/+attachment/5439784/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905080
Title:
I started some investigation with the pulseaudio upstream and the issue
is caused by the fact only the currently selected profile receives
updates of the the plugged/available state since PA13 and that conflicts
with the feature of switching the unavailable profiles away. They never
get back from
Hello. Like mentioned in #1905078, I don't have the apport package
installed and don't plan to do so due to various reasons. Right now I'm
working with PA downgraded from 1:13.99.1-1ubuntu3.7 to
1:11.1-1ubuntu7.10 that doesn't exhibit such problems.
--
You received this bug notification because
Hi. Sorry, I understand you have a process, but ... the ubuntu-bug tool
is broken/annoying/collecting info that I don't wanna disclose and I
always uninstall apport. Moreover, I've already downgraded all relevant
PA packages from 1:13.99.1-1ubuntu3.7 to 1:11.1-1ubuntu7.10, since the
second bug
Upstream report:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1032
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905080
Title:
After upgrading from Ubuntu 18 to 20 pulseaudio
I had a talk with the upstream on #pulseaudio IRC channel and the issue
has not been resolved upstream yet. The guys expect the fix before the
PA 14 release.
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1032
It seems the fix went to 13.99.2 and the Ubuntu 20.04 version is
13.99.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905078
Title:
pavucontrol duplex profiles disappeared for SB Audigy after
I just received some tip on the #pulseaudio IRC channel ...
The above bug has been fixed with the following merge requesrt:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/349
Could you please patch/upgrade the package?
--
You received this bug notification because you
I just studied the PulseAudio 13 release notes and it is probably
related to the following "improvement" ...
::Automatically switch away from unavailable card profiles::
How about restoring the profile when it becomes available again?
--
You received this bug notification because you are a
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905078
Title:
pavucontrol
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905080
Title:
After upgrading
Public bug reported:
Before the upgrade the HDMI 4 digital stereo output was chosen
automatically for my nvidia GF card and was usable by the players
immediately after turning the TV on. After the upgrade I have to switch
the profile from Disabled to HDMI4 each time I turn the TV on. It
doesn't
Public bug reported:
I just upgraded from Ubuntu 18 to 20 and analog stereo duplex profile is
gone. The duplex profile was there and was working properly before.
The following seems to be related:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/750
** Affects: systemd (Ubuntu)
Hello Alex. It's ok, I was unsure with the security classification. The
attackers could cross the boundaries as a direct result of the user's inability
to encrypt disc drives using BitLocker, so ... it isn't a "hidden" security
problem, but it still affects the security at certain level.
After upgrading to Linux Mint 16 that comes with xfce4-session
4.10.1-1ubuntu1 and xfce4-xkb-plugin 1:0.5.6-1 the issue doesn't occur
anymore. Just the Num Lock LED still gets inverted, but that's a
different story related to the evdev driver. I reported that in the Red
Hat Bugzilla and trying to
** Also affects: linuxmint
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198539
Title:
bluetooth-applet missing, while announced in the description.
To
https://bugzilla.gnome.org/show_bug.cgi?id=682860
It seems the applet has been removed upstream ...
** Bug watch added: GNOME Bug Tracker #682860
https://bugzilla.gnome.org/show_bug.cgi?id=682860
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems 'mate-bluetooth-applet' is the 'bluetooth-applet' fork and is
still available ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198539
Title:
bluetooth-applet missing, while announced in
Hello guys. In my case the plugin periodically forgets the settings due
to the following USB error ...
Nov 3 13:24:17 Work kernel: [ 6966.224035] hub 8-0:1.0: port 1 disabled
by hub (EMI?), re-enabling...
It appears approximately once a hour
The same happens when I unplug and re-plug the
Hi Raymond.
I was able to reproduce the issue on a different computer with the same
soundcard. The biggest problem apparently lies in the way PulseAudio controls
the volume sliders. As it automatically sets the PCM and Front sliders to 100%
for PA volume levels 30%, that consequently leads to
Ok. Sounds reasonable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180986
Title:
X Segmentation fault with dual-head config on Matrox G45FMDVP32DB
/32MB /DVI /VGA
To manage notifications
** Attachment added: xorg configs logs +
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3684932/+files/mga-dual-head-bug.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello.
After resolving the following dual-head related crashes ...
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1180986
... a new problem was encountered.
I get only a black screen when starting X with dual-head config.
However, when I switch to a
maybe some additional notes
The first try ( xorg.conf-1.txt / Xorg.0.log-1.txt ) leads to a black screen on
both monitors ...
The second try ( xorg.conf-2.txt / Xorg.0.log-2.txt ) leads to the same content
on both monitors ...
The third try ( xorg.conf-3.txt / Xorg.0.log-3.txt ) leads to a
I just did some tests here ...
Even when the screen is black in the first case, the signal seems to be present
on the monitor plugged in the D-SUB connector (it says it's receiving
1024x768x75Hz with 60kHz hsync). The second monitor plugged in the DVI
connector [via DVI to DSUB converter]
** Attachment added: Xorg.0.log-3.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685159/+files/Xorg.0.log-3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: xorg.conf-2.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685156/+files/xorg.conf-2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log-1.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685155/+files/Xorg.0.log-1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log-2.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685157/+files/Xorg.0.log-2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: xorg.conf-3.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685158/+files/xorg.conf-3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: xorg.conf-1.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1183420/+attachment/3685153/+files/xorg.conf-1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Tormod.
Thanks for the quick response. The PPA package build is going to start
in 10 hours and therefore I tried to rebuild the package for quantal by
myself. It stopped crashing, but it still doesn't work with dual-head. I
get only a black screen when trying dual-head. It works correctly
Strange ... after switching to single screen config and then back to
dual-head, everything works correctly ...
I have to do this ritual after each reboot, so it seems the card isn't
correctly initialized when going directly into dual-head.
--
You received this bug notification because you are a
** Also affects: linuxmint
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180986
Title:
X Segmentation fault with dual-head config on Matrox G45FMDVP32DB
Hello Tormod.
I finally found some time to collect the backtrace.
Jumping to 0x is unhealthy ...
---
#0 0x in ?? ()
#1 0xb6fda380 in MGACrtc2FillStrip (pScrn=pScrn@entry=0xb7ff6838) at
../../src/mga_driver.c:3170
#2 0xb6fdba2a in MGAScreenInit
Hello Tormod.
This was the first time I tested Matrox dual-head with Ubuntu. I'm not
100% sure if i remember that correctly, but I think it worked correctly
with Mageia 2. Of course they could have completely different component
versions and local patches. I tried to figure out what component the
Public bug reported:
Hello.
We're experiencing problems when running X server configured for dual-head with
Matrox G45FMDVP32DB.
The crash doesn't appear with single screen config.
lspci -nn
-
02:00.0 VGA compatible controller [0300]: Matrox Electronics Systems Ltd. MGA
G400/G450
** Attachment added: Xorg.0.log-mga-dual.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1180986/+attachment/3678657/+files/Xorg.0.log-mga-dual.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log-mga-dual-xinerama.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/1180986/+attachment/3678656/+files/Xorg.0.log-mga-dual-xinerama.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi Raymond.
I can confirm, that my soundcard is dead. I tried other distros and test
it in a different computer. So, I need to find a replacement. I can't
continue with testing. It's always frustrating, when a piece of HW is
destroyed by SW control.
Regards,
Jaromir.
--
You received this bug
Hello Joseph.
Few hours ago a new mainline kernel (3.9.1) was released, so I tested
3.9.1 instead
RESULT : It works correctly !
--
/dev/sda:
Timing cached reads: 924 MB in 2.00 seconds = 461.21 MB/sec
Timing buffered disk reads: 168 MB in 3.01 seconds = 55.77
Yes there is. And I don't see any problem with that. It works absolutely
correctly with ALSA (even when I set the bass and treble to much higher
values). As this is done on the hardware level, there shouldn't be any
distortion even when the highest possible bass and treble levels are
set.
--
You
I just tried to set the bass level to the max and play the testing track
with pulseaudio while checking the maximum usable volume. The distortion
appeared sooner (lower volume level), but then I heard just one loud
crack and then silence. I'm affraid, that my soundcard died I hear
only
** Attachment added: pulseverbose.log
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1176528/+attachment/3668454/+files/pulseverbose.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: alsa-info.txt
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1176528/+attachment/3668476/+files/alsa-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176528
The pulseverbose.log contains the following:
1.) playing with Audacious/ALSA ; volume set to 100%
2.) switching to pulseaudio ; volume set automatically to ~70%
3.) keeping pulseaudio ; changing the volume to 100%
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello Raymond.
Could you please tell me what information is missing?
Thanks,
Jaromir.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176528
Title:
Sound distorted with pulseaudio when the player
The package version:
pulseaudio_1:2.1-0ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176528
Title:
Sound distorted with pulseaudio when the player volume gets over 97%
(tested with
Public bug reported:
Hello.
We're experiencing an issue with performance of the 2nd harddrive (/dev/sdb)
when running Ubuntu kernels.
The system has the following 2 UATA harddrives:
/dev/sda:
Model=WDC WD1200JB-75EVA0, FwRev=15.05R15, SerialNo=WD-WMAEL1235051
Config={ HardSect NotMFM
Hello.
I'm unable to run apport-collect, but I found the following in the dmesg
log:
[2.126156] ata2.00: simplex DMA is claimed by other device, disabling DMA
[2.192790] ata2.00: configured for PIO4
It seems the same problem has been reported here for DELL PowerEdge 1600SC:
** Attachment added: dmesg output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1176993/+attachment/3667135/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176993
Title:
00:0f.1 IDE interface: Broadcom CSB6 RAID/IDE Controller (rev a0) (prog-if 8a
[Master SecP PriP])
Subsystem: Dell Poweredge SC600
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B-
** 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/1176993
Title:
Very poor performance of the 2nd UATA harddrive (works well with
Tested with mainline kernel ... 3.5.7-03050711-generic taken from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
the same result ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176993
Title:
So ... the only correctly working from the tested kernels was ...
vmlinuz-3.4.34-desktop-1.mga2 ... taken from Mageia 2. Don't know if
there are any Mageia specific patches applied for this issue ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Hello.
I get a sound distortion when playing via pulseaudio and having the player
volume set to 98% or higher.
The problem doesn't occur when playing via ALSA. The sound system has great
reserves.
My soundcard:
05:02.0 Multimedia audio controller [0401]: Creative Labs SB
** Also affects: linuxmint
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077975
Title:
MACH64 video driver crashes with Mach 3D Rage Pro
To manage
Public bug reported:
Hello.
I'd like to report a regression. Previously the mouse wheel could be
used for changing the volume. Unfortunatelly that doesn't work in the
current version (3.2.3-1ubuntu1) anymore. The same problem has been
reported and fixed in case of Debian:
Probably related links:
http://redmine.audacious-media-player.org/issues/119
https://github.com/audacious-media-player/audacious-
plugins/commit/b5612773bb620dfbee9c54f8dfa8fa5ce0d87694
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello guys. It crashes in my case too and the vesa driver doesn't work
correctly in my case (broken windows and panel). Mageia 2 runs perfectly
with the same driver. Could you please apply the upstream patch and make
the package available for testing?
--
You received this bug notification
65 matches
Mail list logo
