Ok, why is this no longer listed as affecting Kubuntu, when the bug only
appeared in Kubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
Title:
hplip Error 5012 on Kubuntu but not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049935
Title:
Crash on connecting Sierra Wireless mobile hotspot
To manage notifications about this bug go to:
Public bug reported:
ModemManager generated some error messages when I connected my mobile
hotspot to charge it. It also doesn't appear in the list of available
connections as the documentation suggests it should.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: modemmanager
apport information
** Tags added: apport-collected
** Description changed:
ModemManager generated some error messages when I connected my mobile
hotspot to charge it. It also doesn't appear in the list of available
connections as the documentation suggests it should.
ProblemType: Bug
Finally figured out how to add a second package to the bug report, yay
me?
** Also affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-meta in Ubuntu.
Ok, just another note- I reinstalled Lubuntu with hplip and hplip-gui,
and did NOT get Error 5012. Furthermore xSane detected the scanner right
off the bat instead of requiring me to power- cycle the printer.
** Summary changed:
- Error 5012 on Kubuntu but not Lubuntu
+ hplip Error 5012 on
apport information
** Tags added: apport-collected
** Description changed:
I first installed this printer on a computer running Lubuntu. After a
few shenanigans getting hp-setup to work properly, I got everything
working.
When I switched back to Kubuntu, however, I started having
apport information
** Attachment added: CupsErrorLog.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254318/+files/CupsErrorLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254319/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254320/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
apport information
** Attachment added: Locale.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254321/+files/Locale.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254322/+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/1034049
Title:
hplip
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254323/+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/1034049
Title:
hplip
apport information
** Attachment added: PrintingPackages.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254324/+files/PrintingPackages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254325/+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/1034049
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254328/+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/1034049
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254326/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254329/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
Title:
Just added apport information for my Lubuntu install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1034049
Title:
hplip Error 5012 on Kubuntu but not Lubuntu
To manage notifications about this
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1034049/+attachment/3254327/+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/1034049
Public bug reported:
I first installed this printer on a computer running Lubuntu. After a
few shenanigans getting hp-setup to work properly, I got everything
working.
When I switched back to Kubuntu, however, I started having problems with
print jobs not going through until the printer was
** Description changed:
I first installed this printer on a computer running Lubuntu. After a
few shenanigans getting hp-setup to work properly, I got everything
working.
When I switched back to Kubuntu, however, I started having problems with
print jobs not going through until the
Have you tried it on Lubuntu 12.04? It doesn't seem to be doing it as of
today's updates.
And yes, I did get my butt in gear and finally start testing the
updates. It looks like this was patched with a post-release kernel
update that also patched most of the touchscreen issues.
--
You received
Unfortunately, I don't have the know-how to switch to a terminal if one
isn't already up, or the actual command to kill it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995053
Title:
Drag Drop to
Public bug reported:
The normal USB creator package (specifically, the GTK one since the
KDE/Qt one wouldn't) doesn't seem to work on lubuntu when installed thru
Synaptic. It doesn't appear in the menu and isn't invokeable thru the
command prompt, at least not thru any command I know. And yet,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998567
Title:
Lubuntu needs a way to make startup USB devices
To manage notifications about this bug go to:
Public bug reported:
When attempting to drag a folder or file from a file-roller window to a
PCManFM window, I get a dialog box which says something to the effect
of, You don't have permissions to extract to . The mouse pointer
becomes stuck as a hand, and the system no longer registers mouse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995053
Title:
Drag Drop to PCManFM window causes system crash
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 908560 ***
https://bugs.launchpad.net/bugs/908560
This is a duplicate of #908560 .
** This bug has been marked a duplicate of bug 908560
Kernel oops following docking dell duo
--
You received this bug notification because you are a member of Ubuntu
So why is this still listed as incomplete when we have good evidence
there is a bug and we're still able to duplicate it, even with the
latest BIOS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I'm going to look into this if I can get any time at work. Should I
test this with or without the driver package installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913164
Title:
Edit: By driver package, I mean the tarball from the eGalax website.
Should I install its contents?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913164
Title:
REGRESSION: eGalaxis Touchscreen
I enabled Proposed on a clean (well, clean then updated) Lubuntu
install, ran the updater. Touchscreen didn't work. Installed the driver
from the latest tarball, still didn't work. Installed eGTouchD, still
didn't work. Hacked my rc.local following the instructions far above,
STILL nothing. Ran
Quote: For eGalaxis devices, its MT_CLS_EGALAX info is not added into current
-precise driver, so it work badly.
@Ling Mei- Is there any way we can get the correct info added or
backported into the driver before release? I'd love to get my
touchscreen working properly the first time around
I'm also running the latest BIOS, and the oops happens every time I plug
it in while running. It also gives me a black screen of death if I try
to resume from suspend or hibernate and have plugged or unplugged it.
Either way, Flash your BIOS isn't a solution. For every story I've
heard of some
I've had trouble with various kernel builds breaking other things that I
don't know how to fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913164
Title:
REGRESSION: eGalaxis Touchscreen Driver
You have to either run it as root (which is very hard in Ubuntu) or add
it to your rc.local and reboot.
From: David Chen
@Anthony, no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There is no font installer in Lubuntu. It shouldn't be very hard to
write one for GTK in a runtime; all it takes is a bit of code- probably
less than a megabyte- to create a .fonts folder in /home or find the
existing one, copy fonts into it, and then update the caches.
This
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975112
Title:
Lubuntu has no graphic font installler
To manage notifications about this bug go to:
Public bug reported:
On an install of the Lubuntu Pangolin beta, the package modemmanager is
missing from the default loadout. This causes networkmanager to be
unable to manage mobile broadband connections. There should be enough
room to install modemmanager considering Lubuntu still includes a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/967132
Title:
modemmanager needs to be added to the Lubuntu default loadout
To manage notifications about this bug go to:
I haven't had any issues related to this bug in a long time, so is there
any reason why its still in the tracker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742516
Title:
gimp-2.6 crashed with
Does it also include the ACPI fix in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908560 ? If not,
there's not much point because the power manager is still totally messed
up and makes basic power management useless.
--
You received this bug notification because you are a
Ok, as someone posted in the UNR thread, here's the nitty gritty about
what's going on here: https://bugzilla.kernel.org/show_bug.cgi?id=38782
. Now, for some reason the Kernel.org folks consider this bug invalid,
which seems like a bloody cop-out considering how quirky hardware
doesn't stop
Editing the local.rc as described here:
https://bbs.archlinux.org/viewtopic.php?id=133851 provides a workaround,
although its a real shame that there's no way to automate this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just something to think about, touchscreen input is supposedly handled
in modern kernels using the module hid-multitouch. Said module
supposedly supports the eGalaxis touchscreen, but it just doesn't work.
Has anyone tried looking at the documentation for hid-multitouch to see
just where its
** 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/913164
Title:
REGRESSION: eGalaxis Touchscreen Driver does not work
To manage
I was unable to test it in the test kernel, but this appears fixed in
Precise with the latest mainline kernel build.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can anyone else confirm that this bug is partially fixed in Precise
using the latest kernel build?
Although the ACPI now fails to properly track when the AC adapter is
plugged in or not, but that's at least better than having to reboot.
--
You received this bug notification because you are a
Looks like this bug might be partially fixed in Precise, although the
touchpad regression is downright frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel oops following
Yes, this bug still exists. Now would someone please help me out here?
I'm getting tired of having the only responses here be from the bot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913164
Title:
** 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/913164
Title:
REGRESSION: eGalaxis Touchscreen Driver does not work
To manage
Invalidating because the bug is no longer reproducible.
** Changed in: partitionmanager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to partitionmanager in Ubuntu.
https://bugs.launchpad.net/bugs/798758
Just a note, from looking at the documentation most of its requirements
are services enabled when the kernel is compiled. Which is several steps
above my level of expertise. Is it possible these kernels are being
built in a way that prevents them from providing the services needed,
which are
I couldn't test that particular kernel release because of massage system
breakage caused by today's run of releases. I already tried dist-
upgrade, and it resulted in a dpkg crash, broken packages, and a lot of
other nastiness including disabled networking. If you can let me know
when the breakage
And, is there any way these patches can be uploaded to a PPA? I can't
seem to get them to install in Kubuntu Oineric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904569
Title:
Linux 3.0.0-15
So for AMD64 on Oineric, which one should I use, the 3.0.15 one (even if
I'm running 3.0.14) or the mainline one which calls for 3.2 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904569
Title:
Public bug reported:
As the title says, the Dell Inspiron Duo (AKA the Inspiron 1090)
generates a black screen on resuming from sleep, requiring a hard power-
down and reboot. This appears to be similar to the SCI_EN bug that
manifested itself during the Lucid testing cycle on Dell laptops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913848
Title:
Black screen on resume from sleep
To manage notifications about this bug go to:
Looks like your stack dump is identical to mine, so I shouldn't need to
post it unless someone asks for it.
By the way, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/913848
is the one I filed on the black screen resume issue. The more attention
we can get from Dell Duo users, the more heat
Public bug reported:
This is a regression. The eGalaxis touchscreen driver as downloaded from
the official website simply doesn't work on my Dell Inspiron Duo. It
does in 11.10, so I see no reason why it shouldn't work. I have attached
a copy of the current (as of this writing) version of the
** Attachment added: eGTouch_v1.01.1014.L-x.tar.gz
https://bugs.launchpad.net/bugs/913164/+attachment/2661395/+files/eGTouch_v1.01.1014.L-x.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: egalax egalaxis touchscreen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913164
Title:
REGRESSION: eGalaxis Touchscreen Driver does not work
To manage notifications about this bug
The way mine crashes, I'm just going to take a photo of the trace on the
screen and see if that helps. At least next time I'm at home; my camera
isn't with me because I'm at work. It looks like the Duo is having ACPI
quirk issues the way the early Arrandale systems did- it seems to have
wake from
I'm having a similar problem with my Duo, except it also sometimes
happens when I connect the AC adapter to the main power socket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/908560
Title:
Kernel
I'm having this bug issue as well in Muon. It hangs at 53% of installing
new updates on a fresh install, with something about running dpkg
being the only sign of what might be messing up. Could be a dpkg
problem, could be a packagekit problem, or a muon problem, who knows?
--
You received this
Public bug reported:
A few minutes after boot, three identical Akondai messages appear in the
notification area, complaining that Nepomuk is disabled. Which its
supposed to be. Is there any way we can add another setting to make
Akondai stop complaining?
This bug happens in both i386 and AMD64
Shame I didn't get that message earlier; I've been using a custom-built
PC since June and haven't had this problem. =/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779871
Title:
Macmini 3,1 kernel
Screenshot attached.
** Attachment added: snapshot1.png
https://bugs.launchpad.net/ubuntu/+source/kubuntu-low-fat-settings/+bug/874569/+attachment/2545816/+files/snapshot1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The workaround in post 25 worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742516
Title:
gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK
theme)
To manage
Public bug reported:
Binary package hint: partitionmanager
Partition Manager hangs at 0% when attempting to write a new partition
table to a Sandisk Cruzer USB stick, or modify partitions on said
device. I haven't been able to check it with other devices,
unfortunately.
ProblemType: Bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798758
Title:
Hang when working with USB device
To manage notifications about this bug go to:
Ok, I went looking through the KDE log viewer a while back, but couldn't
find anything. Can you give me any advice for what logs I should look
for or post, to see if I can find something helpful? There's no way this
bug is only affecting me.
--
You received this bug notification because you are
Thanks. Its been so long since I've had a bug worth reporting, that I
forgot you invoke Apport using ubuntu-bug, which explains why I got an
error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779871
Public bug reported:
Upon shutdown- after Plymouth has disappeared and the screen gone blank,
the power light turns off on the computer but the three keyboard lights
(using a standard PC keyboard here) start blinking. If I don't
disconnect the power, attempting to boot by pressing the power
I have this problem too on Maverick with a Dell Inspiron 1564. I can
provide lspci and other information upon request.
--
intel graphics turbo disabled
https://bugs.launchpad.net/bugs/651104
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Visibility changed to: Public
--
kcmshell4 crashed with TypeError in __init__()
https://bugs.launchpad.net/bugs/644047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Can you allow me to look at #630577 ? Right now it says I don't have
permission to view it.
--
kcmshell4 crashed with TypeError in __init__()
https://bugs.launchpad.net/bugs/644047
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
So does this mean we're very likely to see it fixed in Maverick? I
haven't been able to test Maverick much due to various intel driver
issues and x.org breakage problems.
--
Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)
https://bugs.launchpad.net/bugs/594837
You received
This PPA appears to have solved it on my Inspiron 1564, which is i3
based.
--
Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)
https://bugs.launchpad.net/bugs/594837
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Doesn't seem to be in the suppository, or at least not as of now. Should
I give it a few minutes more and try later?
Also: Did this make it in time for the Beta 1 freeze?
--
Booting with graphical renderer leaves the system at textual login: screen
https://bugs.launchpad.net/bugs/538214
You
Ok, got it and installed.
On initial shutdown, I saw a broken pipe for a few moments.
On restart, it flickered thru several text screens and showed an fcsk
check (sp?) before finally dumping me into the bootsplash. Boot went
normally from there.
Next shutdown showed some text before the closing
Why was this listed as milestoned for Beta 2 instead of Beta 1? This bug
makes Ubuntu completely unusable for people who don't know or don't
remember the keystroke that switches them back to the desktop.
--
Booting with the framebuffer renderer leaves the system at textual login:
screen
Its fixed in that the current version of Plymouth will dump you to a
text login screen, from which you can switch to a real desktop if you
know the function keystroke for it. The fix for that is milestoned for
beta 2.
--
gdm/x fails to start with error Broken Pipe at boot in Xubuntu
I had this last night as well, on an Arrandale-based system. Didn't know
there was a keystroke to get to the desktop, and it also explains why
startx failed with a message saying that X was already running.
--
Booting with the framebuffer renderer leaves the system at textual login:
screen
I had it using the crash reporter icon that appears in the top tray. It
gathered data, got partway through sending, and then whammo. Could not
connect to database. I thought it might've been my cell modem, but I
guess it wasn't.
--
Apport cannot connect to crash database
Public bug reported:
From reading the Ubuntu message board and my own personal experience
with Plymouth having various problems, I'm filing this suggestion box
bug and asking that we remove Plymouth from Karmic until it properly
supports all major video chipsets (including nVidia and intel
Not using that laptop anymore, sorry.
=/
--
[i945gme] Screen seems to be trying to change resolution for no known reason
https://bugs.launchpad.net/bugs/503121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Just crashed on me while I was reporting an X.org crash that happened
when I was removing Alien Arena thru Synaptic. I'd gotten to the point
where Firefox had loaded Launchpad, and wham!
--
apport-gpu-error-intel.py crashed with AssertionError in check_ignored()
I had the same problem or a similar one with the AMD64 version, on an
off-the-shelf Dell Inspiron 1564, i3 based version with Arrandale
graphics. The system would hang on boot, and would sit there for a while
before actually doing anything, if it did anything at all. Removing
Plymouth with
I tried installing Alpha 2 and it doesn't seem to have this issue. Then
again, it seemed fairly random to begin with so I might just have not
done whatever was triggering it.
--
[i945gme] Screen seems to be trying to change resolution for no known reason
https://bugs.launchpad.net/bugs/503121
Public bug reported:
Binary package hint: xorg
Basically, the screen seems to do the thing it does when changing
resolution at random times, without any visible reason for needing to do
so.
ProblemType: Bug
Architecture: i386
Date: Mon Jan 4 21:17:19 2010
DistroRelease: Ubuntu 10.04
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37422048/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37422049/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37422050/Dependencies.txt
**
That's the thing- I didn't do anything special, or at least I didn't
think I was doing anything special, and it would sometimes just flicker
like it was changing resolutions and then go back to the normal one. The
expected behavior was obviously not flickering like that. I was trying
to just
94 matches
Mail list logo
