Public bug reported:
Is self explanitory.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.113-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 14.10
Release:14.10
$ apt-cache policy nvidia-331
nvidia-331:
Installed: 331.89-0ubuntu5
Candidate: 331.89-0ubuntu5
Version table:
*** 331.89-0ubuntu5 0
500 http://us.archive.ubuntu.com/ubuntu/ utopic/restricted
I misread... term.log does say somethign interesting:
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-25-generic
/boot/vmlinuz-3.16.0-25-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-25-generic
Public bug reported:
Here is syslog from start of using NetworkManager to connect to my
company's network to when the service failed to connect:
Nov 24 11:05:28 mback NetworkManager[873]: info Starting VPN service 'vpnc'...
Nov 24 11:05:28 mback NetworkManager[873]: info VPN service 'vpnc
bugbot added tag: karmic, but this bug centered around the clumsiness of
display management with laptop docking affects all versions from karmic
through natty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, this is the right incantation. I've brushed it up a little:
$ cat ~/bin/dock
#! /bin/sh -e
xrandr --output LVDS --off --fb 3200x1200 \
xrandr --output DFP1 --auto --output CRT1 --auto --right-of DFP1
$ cat ~/bin/laptop
#! /bin/sh
xrandr --output CRT1 --off 2 /dev/null
xrandr --output
** Also affects: fglrx
Importance: Undecided
Status: New
** Also affects: gnome-control-center
Importance: Undecided
Status: New
** Also affects: x11-utils
Importance: Undecided
Status: New
** Project changed: fglrx = fglrx-installer (Ubuntu)
--
You received this
The packages affected by this bug are fglrx, compiz, gnome-control-
center (gnome-display-properties), and x11-xserver-utils (xrandr). I
tried my best to add the appropriate projects to the Affects section,
but I'm unfamiliar with launchpad still could have made a mistake in
attribution.
I'm
I don't think this should have been put into expired state. It's still
an issue that xrandr display settings is really finicky with compiz
fglrx. I just crashed my box a little while ago and was fiddling with
this again -- with not perfect success... I had to look back at this
bug report to
I found an xrandr invocation (yes, as in magick) cocktail that seems to
work not bollix up the screen. Man this thing is finicky!
$ cat /usr/local/bin/dual-monitor
#! /bin/sh
# fglrx-based script to do multi-monitor on my T400 box
xrandr --output LVDS --off --fb 3200x1200 \
xrandr --output
BTW -- instead of compiz -- this may be more an issue of xrandr -vs-
fglrx driver issue. We should also think of this as an fglrx -vs-
display settings bug, because when first docked, the display settings
app doesn't see the newly docked monitors -- hence the /need/ for the
script in the first
Well... I update every _daily_, and the issue persists. I have a log of
xrandr when this happens... it happens when I try to switch from Laptop
to Dual monitor with the previous xrandr script.
Screen 0: minimum 320 x 200, current 3200 x 1200, maximum 3200 x 3200
LVDS connected (normal left
ClamAV is what I am using, but... My corporate account has a virus
checker integrated in it's proxy also detects Malware (or Virus) in
this package:
URL:
The above, by the way, was found when I tried to just copy the deb URL
into a browser... It's the browser that reported all this info.
OK, it looks like this is all might not be being caused by Ubuntu, or
Mint at all, as just now I was able to upgrade (on Natty) from home.
It's probably being
Yes -- this is exactly the same, submitted as a question instead of a bug. So,
it affects LinuxMint as well as Ubuntu.
From: Fabien Tassin f...@ubuntu.com
To: mb...@yahoo.com
Sent: Tue, April 19, 2011 1:31:39 PM
Subject: [Bug 765087] Re: 403 VirusFound messages
How do I find out the version that I have, and what version are you
confident fixes the issue?
--- On Thu, 2/24/11, Charlie Kravetz charlie-...@ubuntu.com wrote:
From: Charlie Kravetz charlie-...@ubuntu.com
Subject: [Bug 650433] Re: system-config-printer.py crashed with SIGSEGV in
What info do you want?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/650433
Title:
system-config-printer.py crashed with SIGSEGV in cupsArrayFind() --
while trying to add smb printer (with wrong
With Maverick, now I am able to left-click and drag across screens...
I'm not certain which setting in compiz enabled this... However one
issue still remains especially WRT VNC clients...
My job requires me to access offline systems that span multiple
monitors. Coincidentally my laptop when
It hasn't happened in a while -- I'll reopen if it comes back to haunt
me.
--
gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion() on
either locking the screen or unlocking it.
https://bugs.launchpad.net/bugs/647837
You received this bug notification because you are a
Thinking about this more... There are situations where I want full-
screen and maximize to mean different things... At work with VLC, it
definitely means span all screens so that F11 in Vinagre or Remmina
can work effectively with my remote workstations, so that some games can
span multiple
Public bug reported:
Binary package hint: xorg
Previous to this weekend's x.org update, the max resolution possible on
this cpu/chipset (ThinkPad T400 with integrated Radeon HD 3400) was
3200x1200 (I use this for dual external monitors). I am instead
currently limited to 3040x1200 which is not
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/650522/+attachment/1650087/+files/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/650522/+attachment/1650088/+files/CurrentDmesg.txt
** Attachment added: Dependencies.txt
@Travis -- I see hints from Cornelius and you about the issue in the
postings, but will you fully describe the reason for making this
change here (or provide a link), because to us it just seems like this
is a misfeature and inconvenient...
I think I remember the menu gnome sometimes folding
@cometdog - Thanks for the tip... I've been using the Alt-F8 workaround
for some time... but it is still inconvenient.
My use case is that I need to control multi-headed remote workstations
via VNC. I also sometimes have large spreadsheets and text editing that
spans multiple screens. So, I
It seems that others have had success working around this bug, but I
have to confess that I am at a loss... With compiz enabled, I cannot
drag-resize windows to larger than one screen. Neither can I make full-
screen of an application use up multiple screens... this is especially
problematic with
After a couple of days updating Karmic, this bug went away. I have no
idea if it is an intermittent thing, or if someone just caught it
fixed it, or if rebooting solved the issue.
--
xrandr reports incorrect maximum screen size
https://bugs.launchpad.net/bugs/449867
You received this bug
Well, this new behavior is equivalent of breaking compiz for me. I
was very comfortable with the old behavior of compiz naturally allowing
windows to be resized across displays... I'll try the workaround, but
this new behavior is counterintuitive, and should be treated as a bug.
It's only with
Public bug reported:
Binary package hint: compiz
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
$ apt-cache policy compiz
compiz:
Installed: 1:0.8.4-0ubuntu2
Candidate: 1:0.8.4-0ubuntu2
Version table:
*** 1:0.8.4-0ubuntu2 0
500 http://us.archive.ubuntu.com
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/34417701/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34417702/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34417703/Dependencies.txt
**
Public bug reported:
Binary package hint: compiz
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
$ apt-cache policy compiz
compiz:
Installed: 1:0.8.4-0ubuntu2
Candidate: 1:0.8.4-0ubuntu2
Version table:
*** 1:0.8.4-0ubuntu2 0
500 http://us.archive.ubuntu.com
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/34418020/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/34418022/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34418023/Dependencies.txt
**
Public bug reported:
Binary package hint: x11-xserver-utils
$ lsb_release -rd
Description:Ubuntu karmic (development branch)
Release:9.10
$ apt-cache policy x11-xserver-utils
x11-xserver-utils:
Installed: 7.4+2ubuntu3
Candidate: 7.4+2ubuntu3
Version table:
*** 7.4+2ubuntu3 0
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/33560708/BootDmesg.gz
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33560710/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33560712/Dependencies.txt
**
Public bug reported:
Binary package hint: samba
Tried upgrading today from what was most recent to today's version of
SAMBA. Expected the updater to either merge the conf file or use prev,
and it crashed instead.
Tried a 3-way merge on the conf file... unsuccessful. Upgrade Manager
came back
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32872203/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/32872204/DpkgTerminalLog.gz
--
package samba-common 2:3.3.2-1ubuntu3.2 failed to install/upgrade: subprocess
Public bug reported:
Binary package hint: samba
Tried upgrading today from what was most recent to today's version of
SAMBA. Expected the updater to either merge the conf file or use prev,
and it crashed instead.
Tried a 3-way merge on the conf file... unsuccessful. Upgrade Manager
came back
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32872203/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/32872204/DpkgTerminalLog.gz
--
package samba-common 2:3.3.2-1ubuntu3.2 failed to install/upgrade: subprocess
This has appeared for me on Jaunty during sudo apt-get update:
Hit http://tw.archive.ubuntu.com jaunty-security/multiverse Packages
Get:4 http://tw.archive.ubuntu.com jaunty-updates/main Packages [129kB]
99% [4 Packages bzip2 0]
I have no been able to reproduce after reinstall
** Changed in: ubuntu
Status: Incomplete = Invalid
--
after dist-upgrade on 3/19, black screen on login
https://bugs.launchpad.net/bugs/346020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
to tell. I'll assign this to myself see if I
can't reproduce it again.
** Changed in: ubuntu
Assignee: (unassigned) = mback (mback)
Status: New = Incomplete
--
after dist-upgrade on 3/19, black screen on login
https://bugs.launchpad.net/bugs/346020
You received this bug notification
** Description changed:
On Ubuntu Jaunty I did a dist-upgrade on 3/19 @ about 6PM.
+ I'm on a Lenovo Thinkpad T400 running amd64.
I rebooted, and went sucessfully through grub -- but after this, I am
greeted with a black screen (it flashes dark/black a couple of times
like it's trying
Public bug reported:
On Ubuntu Jaunty I did a dist-upgrade on 3/19 @ about 6PM.
I rebooted, and went sucessfully through grub -- but after this, I am
greeted with a black screen. There is no progress bar, only little red
bits of distortion at the top of my screen -- as though the resolution
** Description changed:
On Ubuntu Jaunty I did a dist-upgrade on 3/19 @ about 6PM.
I rebooted, and went sucessfully through grub -- but after this, I am
- greeted with a black screen. There is no progress bar, only little red
- bits of distortion at the top of my screen -- as though the
Public bug reported:
From jaunty 3/20/09 recovery... trying to boot to root console with
networking.
I cannot boot by default with networking -- I get an IP address, but
DHCP DNS is broken, so I can't try to download any latest fix via apt-
get update/dist-upgrade. There is an error on the
** Description changed:
On Ubuntu Jaunty I did a dist-upgrade on 3/19 @ about 6PM.
I rebooted, and went sucessfully through grub -- but after this, I am
greeted with a black screen (it flashes dark/black a couple of times
like it's trying to resolve the resolution). There is no
Public bug reported:
$ lsb_release -rd
Description:Ubuntu jaunty (development branch)
Release:9.04
$ apt-cache policy gnome-display-properties
W: Unable to locate package gnome-display-properties
$
IOW it is the latest as of yesterday Mar 4th. It has been this way
since I started
Public bug reported:
$ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04
$ apt-cache policy gnome-display-properties
W: Unable to locate package gnome-display-properties
$
IOW it is the latest as of yesterday Mar 4th. It has been this way since
I started using Jaunty
Public bug reported:
Ubuntu 8.10
IBM Thinkpad T43
FGLRX Driver
Docking station with two 1600x1200 monitors attached.
Upon docking my Thinkpad to its docking station, I expected the Screen
Resolution application to be able to see both of my external monitors
that I am able to conveniently
Hello pestilence,
I am just a humble user subscribing to this bug, not a Ubuntu help
person... I had problems a while back with Dapper, but I have had no
such problems with Gutsy and my IBM ThinkPad T43... I have the same HW
as I did with Dapper, I believe I am still using the ipw2200 driver, and
You can cancel this -- I opened firefox successfully turned on one
extension (repeat) -- one by one it came up without problems... I
don't know what extension(s) caused this.
--- John Vivirito [EMAIL PROTECTED] wrote:
Can you do as stated above but remove them one by one and check after
you
Public bug reported:
Added the following add-ons:
Adblock Filterset.G Updater 0.3.0.4
Adblock Plus 0.7.2.2
Distrust 0.5.8
Fasterfox 2.0.0
NoScript 1.1.4.5.061030
Password Exporter 1.0.6
Crash on restart of firefox
** Affects: firefox (Ubuntu)
Importance: Undecided
Status:
** Attachment added: Complete Crash Report
http://librarian.launchpad.net/5198254/_usr_lib_firefox_firefox-bin.1000.crash
--
After adding Extensions, Firefox Crashes
https://launchpad.net/bugs/73658
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
52 matches
Mail list logo
