I am one of those affected by this bug. I tried the 340 driver made by this
PPA as a workaround and it works great and resolves my issue:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640
--
You received this bug notification because you are a member of Ubuntu
Chris,
I followed your instructions but it didn't work complaining about a
permission issue. So I ran it with sudo and it seemed to work.
$ sudo ubuntu-bug /var/crash/nvidia-340.0.crash
But it still appears that the bug didn't attached the crash report.
Sorry, I tried.
On 8/8/21 6:30 PM, Chris
Public bug reported:
My two older Zotacs use the NV 340.108 driver and both are having the
same issue. After the latest dist-upgrade they boot fine but don't
display video, just a blank black screen with a randomly blinking
cursor. They're headless but I got into both with ssh in order to
If needed I can post or attach the nvidia-340.0.crash file that was
created.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939251
Title:
nvidia driver crashes after kernel upgrade
To manage
Public bug reported:
My two older Zotacs use the NV 340.108 driver and both are having the
same issue. After the latest dist-upgrade they boot fine but don't
display video, just a blank black screen with a randomly blinking
cursor. They're headless but I got into both with ssh in order to
How? When I attempt to using Ubuntu's Software Install it says there
are unmet dependencies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909790
Title:
wireless mouse middle click missing on new
Same thing - no middle click event:
$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Sleep Button
/dev/input/event1: Power Button
/dev/input/event2: Power Button
/dev/input/event4: Logitech Wireless Keyboard
Nope, no middle click event:
$ sudo libinput debug-events
-event2 DEVICE_ADDED Power Button seat0 default
group1 cap:k
-event7 DEVICE_ADDED Video Bus seat0 default
group2 cap:k
-event1 DEVICE_ADDED Power Button
X11 is default and what I normally run. Switching to Wayland did not
help and made no difference to my issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909790
Title:
wireless mouse middle
6_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: marcw 1410 F pulseaudio
/dev/snd/controlC0: marcw 1410 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 31 20:1
Public bug reported:
Upon the first launching of pysolfc, it takes about 4 seconds to open,
which is about the same as when run from 12.04. With each closing and
re-launching of the app it takes progressively longer to open until
finally after 15 or so launches it takes about 10 seconds to open.
Public bug reported:
Undo button does not work. In 12.04 I could press undo an unlimited
number of times. With 14.04 version it doesn't work for even one undo.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-sudoku 1:3.10.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic
Sorry, I have no idea what that's supposed to mean.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993880
Title:
Empathy will not connect to Gtalk after a resume from suspend
To manage
Comments about the attached log file:
18:39 - Started a fresh instance of Empathy. Connected to Gtalk as expected.
~18:40 - Suspended machine.
18:47 - Successfully resume machine. Empathy's state was Offline but trying to
connect.
18:49 - Still trying to connect. Manually changed Empathy's
Public bug reported:
In all previous versions, whatever I resized the Mahjong playing area
(window) to, it stuck after quitting. With this version it reverts back
to original, tiny playing field which then has to be resized in order to
be useful.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995430
Title:
resized playing field in Mahjongg isn't saved
To manage notifications about this bug go to:
Public bug reported:
Empathy will not connect to Gtalk after a resume from suspend. I've
waited several minutes after resuming and it just sits there. The only
way to get it to reconnect is to either restart Empathy or force a
manual reconnection with Edit - Accounts - toggle the Gtalk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993880
Title:
Empathy will not connect to Gtalk after a resume from suspend
To manage notifications about this bug go to:
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marcw 1795 F pulseaudio
/dev/snd/controlC1: marcw 1795 F pulseaudio
BuildID: 20120411015315
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not
found.
Card0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992981
Title:
thunderbird audio and visual notifications don't work
To manage notifications about this bug go to:
Why was this marked invalid?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813255
Title:
resume from suspend fails with 2.6.33-70 update
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/813255
Title:
resume from suspend fails with 2.6.33-70 update
To manage notifications about this bug go to:
Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marcw 1304 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfcff8000 irq 22'
Mixer name
In the past couple days I've figured out a work around for this issue: I
uninstalled gnome-screensaver and installed xscreensaver instead. This
seems to have solved the issue. And I get better screens to boot!
--
resuming from S3 wrongly prompts for password
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: gnome-power-manager
Despite the gconf items
/apps/gnome-power-manager/lock/use_screensaver_settings and
/apps/gnome-power-manager/lock/suspend
both being set to false, I am still
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498884/+files/CurrentDmesg.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498885/+files/Dependencies.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a
apport information
** Attachment added: DevkitPower.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498886/+files/DevkitPower.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member
apport information
** Attachment added: GConfNonDefault.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498887/+files/GConfNonDefault.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/149/+files/Lspci.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498889/+files/ProcCpuinfo.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498890/+files/ProcInterrupts.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498891/+files/ProcModules.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498892/+files/UdevDb.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498893/+files/UdevLog.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification because you are a member of
apport information
** Attachment added: gnome-power-bugreport.txt
https://bugs.edge.launchpad.net/bugs/578542/+attachment/1498894/+files/gnome-power-bugreport.txt
--
resuming from S3 wrongly prompts for password
https://bugs.launchpad.net/bugs/578542
You received this bug notification
Public bug reported:
Binary package hint: gnome-power-manager
Despite the gconf items
/apps/gnome-power-manager/lock/use_screensaver_settings and
/apps/gnome-power-manager/lock/suspend
both being set to false, I am still prompted for a password when resuming my
workstation from S3. I do not
Public bug reported:
Why is the Grip package no longer in the 9.10 repositories? It's been
in all previous releases and as far as I know it's actively maintained.
I had to go to the Grip web site (http://nostatic.org/grip/), download
the source, and build my own in order to use it after building
Public bug reported:
Pysol seems to have gone missing from the Karmic repositories. It was
included in all previous releases afaik.
** Affects: ubuntu
Importance: Undecided
Status: New
--
Where's Pysol?
https://bugs.launchpad.net/bugs/512181
You received this bug notification
I was thinking of trying uswsusp to work around the suspend problem on
my 3810t. But I don't want to reinvent the wheel. Has anyone else
tried this utility? There seems to be a pretty good set of instructions
here: http://en.opensuse.org/S2ram
--
resume from suspend doesn't work (powers off
This bug STILL exists in Jaunty. Neither wildcard nor CIDR designation
works in this list.
For enterprise environments this is simply unacceptable.
--
intrepid: network proxy ignore host list ignored for wildcard
https://bugs.launchpad.net/bugs/284250
You received this bug notification because
Public bug reported:
Binary package hint: ubiquity
In the latest Jaunty beta, as with the Intrepid release, when the
installer gets to step 4 of 7 (partitioning) the graphic for installing
in the largest continuous free space is totally incorrect.
Because a friend and prospective Ubuntu user
Just a me too. Same dmesg as everyone else.
$ uname -a
Linux marcw-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009
x86_64 GNU/Linux
$ free
total used free sharedbuffers cached
Mem: 4055916 9148283141088 0 21952
Michael Vogt wrote:
Was this a virtual machine created with ubuntu-vm-builder?
No. But it wouldn't surprise me if this bug is related to the root
cause found in bug 291337.
--
package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage:
SystemError in cache.commit():
Public bug reported:
Binary package hint: update-manager
This was generated during an upgrade of Hardy
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process
/usr/bin/dpkg returned an error code (1)
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/19101091/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/19101092/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
Public bug reported:
Binary package hint: landscape-client
Failure occurred during an upgrade from Hardy to Intrepid
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage:
ErrorMessage: subprocess post-installation script returned error exit status 1
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/19101121/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/19101122/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
Chandra, now that your two pref - security checkboxes are cleared, just
delete those 2 usrlclassifier* files and you should be good to go. They
will be recreated next time you start Firefox but will not grow beyond
9k. At least that's my experience.
--
[MASTER] High CPU Consumption
My experience is that it will load m3u stream playlists but won't play
them if the Monkey's plugin (whatever that is) is enabled. I
discovered that by trial and error.
For me the only remaining Audacious quirk is that when playing streams
the Playlist Editor insists on showing the individual
A few moments ago I noticed yet another Drupal update was ready for
download and install. That part went fine but I was left with the exact
same post install error as before. And once again, Ivo Mans' workaround
fixed the issue.
So why has this problem been repeated, especially when there is a
Ivo Mans solution is perfect! That Drupal upgrade should never have
gone out in the condition it did.
--
post-installation fails when already configured
https://bugs.launchpad.net/bugs/106689
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I can confirm this problem (yellow Linu when attempting resume) and
solution (rmmod processor) on my Compaq v5209us with Intel video
chipset.
--
[gutsy] [regression] suspend-to-ram: resume is blocked on a blinking cursor
until some random keystrokes are entered - removing processor module makes
Public bug reported:
Binary package hint: firefox
The summary isn't entirely accurate. The new FF profile will start and
display correctly if it's the only FF running. However, if the default
FF profile is already running the new one will not start correctly.
Rather, it starts up the default
I should probably add that this issue exists in reverse as well - if I
open the new profile first and then open the default profile, the wrong
profile opens - it will be the new profile instead of the desired
default profile.
--
new firefox profile doesn't display if default profile is open
Never mind. I discovered that the -no-remote switch allows me to do
what I want - have both profiles open simultaneously. I am confused
however as to why I haven't had to do this previously on other Ubuntus,
even with the same version of FF.
--
new firefox profile doesn't display if default
Once I got past the app armor bug that makes printing not work in the
Tribe5 LiveCD, this bug seems to not exist. Everything I tried printing
on my R380 from Tribe5 seemed to print fine with none of the eject
problems I reported. I suppose I'll just have to live with this bug in
Feisty even
I didn't get a chance to look at this until today and since I received a
notice that Tribe3 was released, I used that one instead of Tribe2.
First off, Booting the LiveCD gives me a warning:
Internal Error
failed to initialize HAL
Not sure if this error is to be expected or not.
The
Public bug reported:
Using the new Gutsy gutenprint 5.0.1 source, diff, and dsc I created a
new deb for my Feisty installation because I noticed that it included a
driver for my new Epson Stylus Photo R380 where the stock Feisty
gutenprint doesn't.
The build and installation went fine with no
Same thing is happening to me on a fresh Feisty install. But http auth
doesn't completely solve things either.
I went through the (quite well hidden) instructions for running htpasswd
first and adding the Alias to the apache2.conf file, all of which did
indeed allow me to achieve a phpmyadmin
Great news! Using the 04/14 Daily Build, all of my previous
difficulries have vanished. All the arrays that I built (I've tried 2
different schemes) now boot flawlessly.
Not sure what the culprit was but it was something that changed between
the 04/12 build and today.
--
Feisty beta1 raid is
*** This bug is a duplicate of bug 84228 ***
https://bugs.launchpad.net/bugs/84228
Today's daily build - 04/14 - completely eliminated all of the remaining
issues I had with this bug. Any of the previous arrays that shouldn't
be appearing on a new install don't and any that should, do. From
Since this looked a lot like my bug (#96511) I tried your workaround.
It didn't work. After adding init=/bin/sh I'm still returned to an
initramfs prompt. Oh well. Evidently 2 different bugs.
--
Feisty: Install to RAID fails to boot after install
https://bugs.launchpad.net/bugs/106238
You
Not positive if the package should be mdadm or not.
** Changed in: mdadm (Ubuntu)
Sourcepackagename: None = mdadm
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Trying once again, I grabbed the latest AMD64 Server daily (04/11.1) but
to no avail - it still fails. This time I'm including screen photos in
case it can help diagnose wherever the heck is happening.
The first 8 prints include the extent of the terminal buffer up to the
initramfs prompt.
Then
Tried the 04/10 alternate daily AMD64 tonight hoping that something's
been fixed. Nope, Still broke. This isn't looking good for using
Feisty for my server.
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You received this bug notification because you are a member of
Well, it was time to try something else. So I grabbed the daily build
(04/09) of the i386 Ubuntu Server instead of my usual AMD64.
Unfortunately I had exactly the same luck with that one as I've had with
the others.
--
Feisty beta1 raid is broken
https://bugs.launchpad.net/bugs/96511
You
I tried the 04/06 (or was it 04/05?) daily build of the AMD64 Ubuntu
Server just to see if there's been any improvement. No change. Still
broke.
Then just on a lark, and because I didn't have anything better to do, I
loaded up the Debian Etch Rc2 AMD64 netinstall daily build (04/06) just
to see
Brian,
I started from scratch tonight building the arrays again as I spec'd in the
first post using the beta1 server install disk.. After a successful install
and a few reboots I was able to get a normal prompt from which I performed a
apt-get dist-upgrade. I noticed this time that I was
*** This bug is a duplicate of bug 84228 ***
I just tried the 03/31 daily build (alternate install - the only one
available) and this bug seems to have been fixed. At least the part I
tried which was raid creation. I didn't test array deletion.
The other raid issue, the main one, still isn't
Ok, thanks for those instructions. Unfortunately, I don't believe
anything good came of it.
First off, trying to get a normal prompt is more difficult than I
originally said; it's probably closer to 1 out of 30 reboots that will
get me to a normal login prompt.
Secondly, I assume the busybox
Thanks Brian. I'd be happy to but can you write, or point me to , a
little step by step of what you're asking?
--
Feisty beta1 raid is broken
https://launchpad.net/bugs/96511
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Having just built a nice dev server I thought I would spend some time
with Feisty beta1. Installation was a breeze (it correctly detected the
onboard NIC that Dapper and Edgy didn't) until it got to partitioning.
I have 4 individual SATA drives (no fakeraid). I wanted a
Yep, I can confirm this. I just got a brand new nicely equipped machine
to use as an all purpose server and since I have the time, I thought I
would play around with the new Feisty beta1 on it. Preferred combo of
software raid1 and raid5 produced the same results as the previous
posters.
Public bug reported:
Binary package hint: gdm
I upgraded the latest gdm (along with 58 other available package
upgrades) this morning from 2.14.6 to 2.14.7 and have now lost my
ability to perform automated logins.
Using gdmsetup and choosing to have a timed login (or automatic login) I
have
I just printed a test job. The same bug appeared. This is the only
entry in the error_log that relates to that print time.
E [14/Jun/2006:21:02:41 -0500] [Job 9] No %%BoundingBox: comment in
header!
--
print jobs stays in Printing state a long time
https://launchpad.net/bugs/48739
--
76 matches
Mail list logo
