Unfortunately nothing has changed. So, the bug is actual.
** 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/1971010
Title:
[vmwgfx]
Looks like with the latest update the problem is solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
[vmwgfx] Desktop is clipped to a rectangle and mouse doesn't work in
With "xorg (Ubuntu)" it is no more reproducible.
File is attached.
** Attachment added: "xorg_para_enabled.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971010/+attachment/5585806/+files/xorg_para_enabled.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
No, I haven't tried that option. How to enable it if have switched login
screen off?
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Funny thing that without any paravirtualization (paravirtualization
interface = none in vbox settings) everything works (but of course much
slower).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug is rather critical as machine is not usable. To report a bug
above it takes me an hour(.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971010
Title:
Screen and mouse doesn't work
To
This happens after upgrade to latest version. Ubuntu is guest for
virtualbox on win10. Video is included:
https://drive.google.com/file/d/1C0IOJlqY-n71PDoVgYfVfrsuHKaUMnvD/view?usp=sharing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Screen and mouse doesn't work
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error:
I'm happy to say that in the current version of the nvidia driver
(nvidia-driver-510) the problem seems to be fixed. I can connect
external monitor and it works flawlessly. Thank you for the help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "syslog.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561606/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "rfkill.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561605/+files/rfkill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "getfacl.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561604/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561603/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561602/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561601/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561600/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561598/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561599/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561597/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561596/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561595/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561592/+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/1960448
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561594/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561593/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1960448/+attachment/5561591/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
Installed blueman to try to figure out if this is related to gnome-
bluetooth - the results are the same.
ProblemType: Bug
DistroRelease:
** 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/1960448
Title:
Sony WF-XB700 Bluetooth headset not detected
To manage
No, the device is not one of the listed ones. Here are the requested
files. Sorry for the delay.
** Attachment added: "files.zip"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+attachment/5560391/+files/files.zip
--
You received this bug notification because you are a member
Forgot to add: I am running dual boot with Windows. Windows does not
have any problem detecting the headset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960448
Title:
Bluetooth headset not
Public bug reported:
Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
Installed blueman to try to figure out if this is related to gnome-
bluetooth - the results are the same.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-bluetooth 3.34.5-4
ProcVersionSignature:
Public bug reported:
When an external display is connected to my laptop, running Ubuntu
22.04, the display is detected and I am sent to the login screen. After
logging in again, the display is not running, although the primary
laptop display works fine. The external monitor is looking for
CPU usage 100%
/var/log/syslog now takes more than 10GiB and grows...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with
Public bug reported:
Ubuntu installation failed after very long waiting for files to copy.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl
Public bug reported:
The Russian interface of the gnome-control-center package contains a typo. A
typo is highlighted in the attached screenshot. Instead of "входе с систему"
you must specify "входе в систему".
Ubuntu version is 18.04.3 LTS
gnome-control-center version is
Even more interesting, your trace actually has
[0] 1012.956817 MMIO32 R 0x100080 0xe100 PFB+0x80 => 0xe100
[0] 1012.956820 MMIO32 W 0x100080 0xe100 PFB+0x80 <= 0xe100
Which means that it _starts out_ at 0xe100. Was this trace done on a
clean boot, or had the nvidia module
(In reply to comment #55)
> So something is initialized by the nvidia driver, which is not touched by
> nouveau but is required for correct operation.
>
> Is there a way I could help? Like dumping register states with/without the
> nvidia init?
You could do a mmiotrace of the nvidia driver. It's
(In reply to comment #63)
> For the first two options I think it could be useful to grep through all
> those dumps collected over the years and check which cards have this set.
Yeah, I'll try to have a look later on.
>
> Option 3 could definately tell if it's only used for a particular memory
>
BTW, interesting. In your VBIOS, it tells us to do
0xcbf2: 7a 80 00 10 00 00 00 00 e0 ZM_REG
R[0x100080] = 0xe000
Which is why that bit gets lost on resume (but not on kexec, since init
scripts don't run, since the adapter is already init'd). Good to know,
that means that
(In reply to AndrewK from comment #73)
> (In reply to nv28m from comment #71)
> > nouveau.agpmode=0 seems to work here too, also after comming back from
> > suspend.
> >
> > Still I think I'm stuck with the modesetting driver with the bit 24 hack in
> > boot/suspend scripts. The scrolling and
(In reply to comment #61)
> At the end I got what I wanted. The winner is:
> nvapoke 00100080 e100
>
> This register is e000 after suspend or after clean boot. So all this
> trouble only because of a single bit was not set ;(
Fantastic! I was secretly hoping that by ignoring the issue
Public bug reported:
ihgih
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
I have a Dell Inspiron N5010 laptop and this bug affected my system.
hope to fix the bug soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759836
Title:
systemd-udevd consumes 100% of CPU
To
** Attachment removed: "Screenshot from 2018-04-24 00-06-51.png"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1766358/+attachment/5126130/+files/Screenshot%20from%202018-04-24%2000-06-51.png
** Attachment added: "Screenshot from 2018-04-24 00-06-51--.png"
Public bug reported:
Today I noticed that the are few processes that load my CPU about 100%.
I check the syslog, and there are lot of following messages:
```
Apr 24 00:09:48 Ilias-HP gnome-shell[1588]: [AppIndicatorSupport-WARN]
Attempting to re-register
Public bug reported:
php-redis v3.1.4 has a critical bug whereby the extension crashes on
attempted usage. I believe the issue is resolved in v3.1.5/6
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
I confirm same kind of problem in Precise.
After update to -ubuntu6.10 ipv4 become to be preferable protocol even on
ipv6-only servers.
%%
telnet google.com 443
Trying 173.194.222.102...
Trying 173.194.222.101...
Trying 173.194.222.113...
Trying 173.194.222.138...
Trying 173.194.222.139...
Trying
The bug is still present in 16.06 xenial, shorewall-5.0.4-1 package. The
patch is really easy, please integrate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096504
Title:
logfile
The bug is still present in 16.04 xenial, bind9-1:9.10.3.dfsg.P4-8ubuntu1
package.
It is described well in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744304
The fix is to edit /lib/systemd/system/bind9-resolvconf.service and add
"RemainAfterExit=yes" at [Service] section. A patch is
(In reply to Alex Perez from comment #14)
> Ping. I am still experiencing problems with incorrect colors with the very
> latest Mesa, compiled from a fresh git checkout today.
Mesa 11.0.3+ work fine on a PPC G5 with a NV34 GPU. Haven't tested much
else. I don't think this is a "core" issue
There is no mention of nouveau anywhere in here, indications of the
other bug are that nouveau vs nvidia doesn't matter, and I see no
indication of DRI_PRIME ever getting set. I believe this is
miscategorized, it's unclear to me why this is in the fd.o bugtracker at
all, sounds like some ubuntu
This bug is a couple years old with no updates, no mention of the
hardware, no mention of software versions, or anything else that would
make this investigatable. Feel free to reopen if it's still an issue and
you can provide fresh information with fresh software versions.
--
You received this
This bug should have been fixed in ~3.18 or so. Re 'ret' being special,
it is, see nvif_unpack macro definition. Feel free to reopen if you're
still seeing pink lines on Kepler GPUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** Bug 89991 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT240
To manage
*** Bug 89991 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/763052
Title:
Ubuntu can't boot on nvidia GeForce GT240 with nouveau drivers
To
*** Bug 78570 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT240
To manage
To anyone looking to pile on with a me too comment: Only do so *AFTER*
verifying that commit 4f6029da is the first bad commit for you.
[Also, check that it's still happening with the latest kernel... 3.17 at
the time of writing.]
BobbyJ: I'm guessing you didn't do that. File your own bug with
Looks like Ben made a more complete fix, now available as part of
http://cgit.freedesktop.org/nouveau/linux-2.6/log/?h=linux-3.18
More specifically
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-3.18id=a522946174b5ae389af0856c422d865a63c70316
Please test confirm.
--
You
All those patches should have made it to 3.16 (and were cc'd to earlier
stable kernels). Does 3.16 work OK for people?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1330785
Title:
Weston on Nouveau
Try updating your intel ddx -- nouveau is not responsible for the
contents of the images it renders when in reverse-prime mode -- the
primary gpu is (in your case, intel).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** Bug 81614 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/925048
Title:
[GTX 580] X seems to hang a login prompt -- PFIFO errors in dmesg
To
(In reply to comment #12)
This bug is affecting me also, see the last duplicated bug. Any progress in
fixing this? Maybe some help in testing (for ex.) required?
It's a bit of a mystery unfortunately. Adding to the annoyance, Ben said
that it does work just fine on his NVC8, although he has the
*** Bug 77371 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217585
Title:
System hangs after some time with nouveau and GT240
To manage
(In reply to comment #40)
I hit this bug upon upgrade from Ubuntu 12.04 to 14.04. I can confirm
nouveau is working in Ubuntu kernel 3.7.10 and it freezes on resume in
3.13.0.
My hardware:
02:00.0 VGA compatible controller: NVIDIA Corporation C79 [GeForce 9400M]
(rev b1) (prog-if 00 [VGA
(In reply to comment #42)
Ilia, I don't know how to do that.
Use your favourite search engine to see how to use 'git bisect'. You may
even be able to find some guide specific to your distro. If you can't
narrow the problem down, we definitely won't be able to help.
--
You received this bug
(In reply to comment #44)
I'm sorry Ilia, I'm a normal user, no kernel developer.
If you're unable/unwilling/whatever-the-reason to do some amount of
debugging, you will be best-served by your distribution's support
channels.
--
You received this bug notification because you are a member
(In reply to comment #29)
Created attachment 95418 [details] [review]
another patch for gddr5 ram
I made this patch using my mmiotrace, but it doesn't help either.
Oh well. Indeed the values in your mmiotrace are different, but your and
Andrew's mmiotrace are the only traces I've seen that
Created attachment 95408
initialize stuff for gddr5 ram
This patch is based on Andrew's mmiotrace. I saw a sequence of init that
I didn't see in other traces for working cards. Andrew -- would be
interesting if you could check it out and see if it helps. The algorithm
I came up with is insane --
Would you be able to do a bisect between 3.7 and 3.8?
Another user identified commit 4f6029da58ba (in bug #67878) which came
in between 3.7 and 3.8 -- perhaps you have the same issue? It's a
different card, so might be different... a bunch of stuff changed
between 3.7 and 3.8.
--
You received
(In reply to comment #37)
I've been following this ticket and attempting to poke around a bit. I just
tested my hardware with various points in the 3.6, 3.7, and 3.7-rc kernels,
and all of those still gave me a non-responsive screen with messages like
the following after resume. e.g., on Linux
(In reply to comment #16)
Created attachment 92127 [details]
kernel log 3.13rc+firmware
What does not in the initrd mean? The files were in /lib/firmware/nouveau
with the names the script gave them (nvd9_fuc*).
But was this /lib/firmware/nouveau available when the nouveau module
loaded?
(In reply to comment #18)
It still doesn't find the firmware after updating the initramfs (sudo
update-initramfs -u -k all), whether it is placed at
/lib/firmware/nouveau/nvd9_fuc*, /lib/firmware/nouveau/fuc*,
/lib/firmware/kernel_version/nouveau/nvd9_fuc* or
(In reply to comment #12)
The blob firmware (in the standard 3.11 kernel) turns the login screen
blank, with no recognisable error in the log.
Was this with mmiotrace'd firmware or with firmware extracted using my
script? If the latter, try moving nvd7_fuc*[cd] over nvd9_fuc*[cd] --
perhaps
Out of curiousity, does using blob pgraph fw help with this issue?
You can extract it yourself by using the instructions at
http://nouveau.freedesktop.org/wiki/NVC0_Firmware/ or you can try using
my script (https://raw2.github.com/imirkin/re-
vp2/master/extract_firmware.py) with the 325.15 blob,
*** Bug 71662 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1243557
Title:
[NVS 4200M] X freeze, unhandled status 0x0080
To manage notifications
A lot of parts of nouveau are rewritten in various kernel versions. A
bunch of stuff happened in 3.5, more in 3.7, more in 3.8. Probably a
bunch of stuff before then too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No (positive) response to re-test request after a month. Closing as
invalid. The driver has been rewritten enough since the original report
that it's very unlikely that the same crash still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Does this still happen with more recent kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075050
Title:
[Dell E6530] Precise installer can't boot to desktop without
nomodeset
To manage
No response to re-test request in over a month. Closing as invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005292
Title:
EOG shows black stripe in pictures
To manage notifications about
This is pseudo-similar to bug 53566 which I closed earlier. Do these
issues persist, or are they all fixed in recent kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041637
Title:
GF114
This is not the appropriate forum to track power management not
supported issues. This is something that's being worked on, when it's
supported, should it not work, feel free to file bugs then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
bugs about it. [Also note that most CPU/GPU chips have
overheat protection.]
OK, Ilia. Where do yo recommend to post such report about power management
not supported issues?
I would recommend sitting tight and waiting for this functionality to be
released. The Nouveau project's devs are well aware
What backlight driver is being used? Please post your dmesg. Are you
booting with acpi_backlight=vendor ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouveau: dark screen after
Can someone confirm that this is fixed in newer kernels as Ben said it
should be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouveau: dark screen after suspend/resume
To manage
Does this still happen with newer versions of the kernel/xf86-video-
nouveau?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005292
Title:
EOG shows black stripe in pictures
To manage
Marking as fixed per the last comment. If this is still an issue, feel
free to reopen with fresh logs/etc from a new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/754711
Title:
[Dell Studio
Re-closing this. The people who reopened posters (a) had totally
different hardware, (b) did not provide any actual info, and (c) didn't
add themselves to cc.
If someone should still have issues regarding backlight, please file a
full issue as instructed by
*** This bug has been marked as a duplicate of bug 33165 ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/706063
Title:
Nvidia GT240 screen corruption after boot
To manage notifications about
It appears that this bug report has laid dormant for quite a while.
Sorry we haven't gotten to it. Since we fix bugs all the time, chances
are pretty good that your issue has been fixed with the latest software.
Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9,
mesa 9.1.6, or
** Bug watch added: Red Hat Bugzilla #830162
https://bugzilla.redhat.com/show_bug.cgi?id=830162
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=830162
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
fedora bug #830162, comment 4 points to the apparent upstream fix:
http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=bf5b4012e9de9f441ab20c40a259c4fb38c146cf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 882878 ***
https://bugs.launchpad.net/bugs/882878
** This bug has been marked a duplicate of bug 882878
With IPv6 disabled, openssh will not forward X connections
--
You received this bug notification because you are a member of Ubuntu
Server Team,
*** This bug is a duplicate of bug 882878 ***
https://bugs.launchpad.net/bugs/882878
** This bug has been marked a duplicate of bug 882878
With IPv6 disabled, openssh will not forward X connections
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 575058 ***
https://bugs.launchpad.net/bugs/575058
** This bug has been marked a duplicate of bug 575058
unable to use asoundconf-gtk application, because /usr/bin/asoundconf Python
script missing by default
--
You received this bug notification because
Bug #376024 alsa-utils missing asoundconf is WONTFIX, so the
resolution for this bug should probably be remove asoundconf-gtk
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/575058
Title:
Upstream commit 9f1b0f0f1ed should fix this segmentation fault:
http://neil.brown.name/git?p=mdadm;a=commitdiff;h=9f1b0f0f1ed0dd4752be65348a24971335cd50e8
This commit is included in 3.2.4 release, consider updating the whole
package.
FYI, below is a gdb stacktrace of mdadm 3.2.3-2ubuntu1:
#0
** Patch added: Upstream fix
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/969384/+attachment/3182621/+files/9f1b0f0f1ed.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969384
Title:
Today I started an update of many packages and muon hung on 71%. This is
not related to etckeeper, but looks related to the pseudoterminal
output, similarly to comment #10. The actually hung process is /bin/sh
(dash), trying to write to stdout.
$ ps -e f #only a relevant part
20736 ?Sl
** Bug watch added: KDE Bug Tracking System #292423
http://bugs.kde.org/show_bug.cgi?id=292423
** Also affects: qapt via
http://bugs.kde.org/show_bug.cgi?id=292423
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug no longer affects me, as well as all other ecryptfs related
bugs! :)
It has turned out that my needs are fulfilled by another solution, much better
in terms of stability AND performance: LUKS.
The difference from ecryptfs from the user's point of view:
1. whole partition/volume is
Public bug reported:
Binary package hint: ubuntu-dev-tools
I've noted that sometimes I need to wait relatively long time for bash
to start, especially after system start and login or resume from
suspend, but may also happen after some heavy disk load (e.g. `grep -r
foo /usr`). I've profiled bash
1 - 100 of 148 matches
Mail list logo
