I don't recall for sure, but I have 'UMASK 077' in /etc/login.defs and
believe the default is 022, so I probably have changed the default. I
also have 'USERGROUPS_ENAB yes', resulting in a mask of 007 for the
debian-spamd account.
In my opinion, amavis's ability to read the ruleset created by
Public bug reported:
ubuntu 14.04.1 LTS
Packages:
spamassassin (3.4.0-1ubuntu1)
amavisd-new (1:2.7.1-2ubuntu3)
This report has to do with a problem between the interaction of the
spamassassin and amavisd-new packages, but the problem is with
/etc/cron.daily/spamassassin.
Public bug reported:
ubuntu 14.04.1 LTS
Packages:
spamassassin (3.4.0-1ubuntu1)
amavisd-new (1:2.7.1-2ubuntu3)
This report has to do with a problem between the interaction of the
spamassassin and amavisd-new packages, but the problem is with
/etc/cron.daily/spamassassin.
Public bug reported:
I configured a usb brother printer correctly (working) on ubuntu 14.04.1.
Then I installed a samba server to share this printer on a windows network
The samba printing from windows machines works correctly. The usb direct cups
printing inform printing OK, jobs completed, but
I found that changing Firefox's theme fixes the problem, but it has to be a
Complete Theme (the one that changes Firefox complete appearence). But, this
is more like hiding the problem instead of fixing it because the problem
persists if I go back to the default theme.
Note: I'm currently
I just tried this with kernel 3.13.0-34.60 and I'm still experiencing
the problem. Brightness set to minimum and not adjustable after
undocking.
I originally encountered another (duplicate?) bug post which suggested
to upgrade the x220's BIOS, so I'm also running the latest BIOS version
(8DET69WW
*** This bug is a duplicate of bug 1308674 ***
https://bugs.launchpad.net/bugs/1308674
This looks like a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308674 ?
FWIW: I have upgraded my BIOS to the latest version (8DET69WW / 1.39)
and I'm still seeing the same problem.
I can add that docking and undocking again re-enables brightness
adjustment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308674
Title:
[Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings
Public bug reported:
Bug report??
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
Public bug reported:
Unable to install programs or update the system; after any attempt I get
this error message.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.1-2ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-20.35~precise1-generic 3.11.10.6
Uname: Linux 3.11.0-20-generic
I've carried out the merge in the linked branch. I was wrong before, the
Debian package does include the Replaces lines, so it's only the
apparmor profile that is ubuntu specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~roger.light/ubuntu/utopic/mosquitto/merge-
debian-1.3.4-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358019
Title:
Merge mosquitto 1.3.4-2 (universe) from Debian unstable
current utopic version 0.15-2ubuntu1:
mosquitto (1.3.4-2) unstable; urgency=low
* Disable bad fake ca test.
-- Roger A. Light ro...@atchoo.org Sat, 16 Aug 2014 10:52:12 +0100
mosquitto (1.3.4-1) unstable; urgency=medium
* New upstream release: http://mosquitto.org/2014/08/version-1-3-4
This also closes bugs #1037892 and #1035328.
The Debian packaging changed so that the dev packages were not
versioned, so it would be best to update debian/control to make
libmosquitto-dev replace libmosquitto0-dev and libmosquittopp-dev
replace libmosquittopp0-dev.
--
You received this bug
Public bug reported:
Trying to run the Supercollider http://supercollider.github.io/ sound
synthesis program on an ARM-based NVIDIA Jetson TK1, I received this
error. I also received this when I tried jack_simple_client
FATAL: cannot locate cpu MHz in /proc/cpuinfo
This is from the Jack
I believe this error
FATAL: cannot locate cpu MHz in /proc/cpuinfo
is related to the Jack Library and I believe it is fixed in the latest source
by this checkin:
https://github.com/jackaudio/jack2/commit/d425d8035b761b4a362c538c41eca874ff4995f0
So, I think updating the jackd library would fix
Public bug reported:
I select new folder, window appears, but cannot enter name in text box
to create new folder.
It seems that some users have this problem, some not. XFE has no
variants, so I'm guessing the problem arises within Ubuntu and
variations in Ubuntu setup.
Please see
I was having a similar problem with my Epson Perfection V33 flatbed and
Xsane. The Xsane community (Mark Buda) pointed out that there is a
problem with Linux handling XHCI mode. I went into my BIOS and disabled
XHCI mode and now my scanner is working normally. I forgot to point out
that my
This bug also affects me. I just want an interface that nothing is sent
out on and with no addresses, for my switch's monitor port.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1314848
Title:
not
I have this bug for years (and still present). This bug report saved my
life, the hda-jack-retask workaround (set the Green Headphone, Front
side to Override and Not connected) worked
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is no solution at present; these are generated at buildtime for
the host OS, so don't vary at runtime. That said, it would help to know
what's different between upstart and systemd here. What's failing
exactly, and why?
--
You received this bug notification because you are a member of
Public bug reported:
DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS
Firefox 29.0 as included with Ubuntu 14.
net.sourceforge.jnlp.LaunchException: Fatal: Read Error: Could not read or
parse the JNLP file. You can try to download this file manually and send it as
bug report to IcedTea-Web team.
;
PyObject* warning = user_data;
This seems a bit like wallpapering over the cracks, but it was the
simplest fix I could come up with.
Roger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860680
I switched to trying to resolve my case of the bug by fixing the cause
of the warning. In my case this is a warning from pango that it could
not find a loadable module.
/usr/lib/i386-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot
open shared object file: No such file or directory'
The
are welcome to distribute it
under certain conditions. See COPYING file for more details.
hp-systray[3194]: debug: Locking: /home/roger/.hplip/hp-systray.lock
hp-systray[3194]: debug: Creating pipe: hpssd (5) == systemtray (4)
hp-systray[3194]: debug: Creating pipe: hpssd (6) == hpdio (4)
hp-systray[3194
I suspect that this is happening because python has hooked itself if
into the GTK logging system. So it looks like _PyErr_WarnEx should
really check whether _PyThreadState_Current is non NULL before
proceding. This rreally looks like a horrible can of worms.
Can the python guys please look at
software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
hp-systray[3456]: debug: Locking: /home/roger/.hplip/hp-systray.lock
hp-systray[3456]: debug: Creating pipe: hpssd (5) == systemtray (4)
hp-systray[3456]: debug: Creating pipe: hpssd (6
This looks like a bug in the python interpreter.
The routine setup_context in Python/_warnings.c looks like this.
setup_context(Py_ssize_t stack_level, PyObject **filename, int *lineno,
PyObject **module, PyObject **registry)
{
PyObject *globals;
/* Setup globals and
This bug is still affecting me in 14.04.
Have looked at this further using gdb. It seems that there is a generic
problem in do_warn when called from systray.py. A number of other bugs
have reported this with different warning messages cuasing the crash. So
anything that causes a warning message
This bug has many duplicates. It appears that systray.py will crash
whenever a warning message is generated. The oither bugs report a number
of different warning messages.
The following bugs are definite duplicates.
#862779
#1046036
#1046635
#1157504
#1287596
#1299676
#1299764
The following are
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug is no longer a duplicate of bug 862779
systray.py crashed with SIGSEGV
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug is no longer a duplicate of bug 862779
systray.py crashed with SIGSEGV
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug
*** This bug is a duplicate of bug 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
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 860680 ***
https://bugs.launchpad.net/bugs/860680
** This bug has been marked a duplicate of bug 860680
systray.py crashed with SIGSEGV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug still exists on 14.04 Trusty Tahr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/860680
Title:
systray.py crashed with SIGSEGV
To manage notifications about this bug go to:
Still happening at 14.04. Managed to do apport-retrace and run gdb. This
is what the stack trace looks like now. It may be another bug is hiding
the first one.
info (gdb)Auto-loading safe path
done.
warning: core file may not match specified executable file.
[New LWP 6922]
[New LWP 7063]
Public bug reported:
Using virginmedia.com mirror with xubuntu 13.10
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-release-upgrader-core 1:0.205.5
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Just did a fresh text install (twice) of 14.04 and the install grub
step failed with exactly the same symptoms. Trying to do things
manually results in a boot where I get dumped into initramfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is still present and another scenario is btrfs. cryptroot is
written under the assumption there is exactly one device that needs to
be decrypted for root to be mounted, which can be very wrong for btrfs.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Another Ubuntu release and this is still broken. As a reminder if you
use the keyscript then you will *not* be able to enter passwords, either
in graphical mode (plymouth) or text mode (recovery).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I just got bitten by this doing a fresh install of 14.04 with two
drives. For whatever reason it decided to write to a different device
than it had previously resulting in an unbootable system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
In both Saucy and Trusty (with Gnome 3.10 and 3.12 respectively),
Synaptic has been taking an inordinate amount of time populating lists
with search results, often resulting in a Force Quit? dialog. But at
least it hasn't crashed. Until now.
The good thing is that packages
Looks like Intel just fixed the incorrect version in the January
microcode so a work-around won't be needed. This report can now be
closed.
File name:
microcode-20140122.tgz
Version:
20140122
Download
Date:
01/22/2014
Status:
Latest
Size:
0.73 MB
Language:
English
Hello,
For my part, I don't understand English... But there is always Google to
translate from one language to another.
The version of gnome-schedule, if outdated, however, is up to date for
version 12.04 (precise) of Ubuntu. So I've sent to you the corrections I
made it to resolve the
in
their website.
I am using Ubuntu 12.04 and the package being installed is
1.17-13.1ubuntu2
Roger R. Cruz
** Affects: microcode.ctl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
File name:microcode-20140122.tgz Version:2014122 Download
Date:01/22/2014 Status:Latest
Size:0.73 MB Language:English
Operating Systems:Caldera Linux*, Chromium OS*, Debian Linux*, Debian 3.1
Linux*, Fedora 8*, Fedora 10*, Fedora 11*, Google Chrome OS*, Linux*, Mandriva
2006 Update*,
Public bug reported:
La version gnome-schedule Plannificateur de tâches GNOME 2.1.1-4, exécutée
sous Ubuntu Precise 12.04.4 LTS, présente le défaut suivant :
Un modèle de tâche exécutable une seule fois (tâche de type at) ne peut pas
être modifié. Lorsqu'on sélectionne ce modèle dans la fenêtre
** Changed in: unity-lens-applications
Status: Triaged = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192081
Title:
Previews for applications are really slow to display anything
To
Public bug reported:
Wi-fi had been working fine, but this morning, nothing doing.
syslog shows many instances of:
warn Activation (wlan0/wireless): association took too long, failing
activation.
Some info which may or may not be relevant:
Removing the network and adding it made no
Public bug reported:
I am generating man pages from docbook xml using xsltproc and
/usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl
My man page contains entries like this for the See Also section:
citerefentry
All I know is that whatever the cause was, it was fixed in 3.12 even in
the rcs. I have no idea what the actual fix was.
Kernel 3.11 end of lifed November last year. I also use btrfs for which
there have been maintenance patches in 3.12.
I followed the Kernel Build and Installation section at
I get same list of missing libs as Riki Villalba (rikivillalba). Tried
installing the dev versions of these libs
eg libavformat-dev , libavdevice-dev etc. Did not help
I have libavdevice53 installed but there is no libavdevice in synaptic
Blender 2.69+svn61239+git201401010427.d8f4cb9 on
You do know that no one knows what the fix is, only that it is in 3.12?
You can see that Timo gave up trying to find it in mid-November. If
Ubuntu is actually going to figure out the fix and backport it, then go
for it. However I am extremely sceptical and had to devise my own
workaround.
--
Kernel 3.12 even in the prereleases fixed this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer work
To manage notifications about this bug
It isn't invalid. This is a very real issue affecting the existing
Ubuntu release.
I have been personally compiling 3.12 kernels from kernel.org as a
workaround that works for me, so I don't need anything.
I'd suggest closing as Won't Fix since Ubuntu won't provide a fix.
--
You received this
If Ubuntu would actually backport the 3.12 kernel to Saucy then go for
it. The kernel team PPA does not do 3.12 for saucy. At a minimum
3.12.6 is needed due to lots of btrfs fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also having the same problem with a LAMP install in 13.10. What in
the world is going on in this day and age.
WHEN WILL A SOLUTION OR ANSWER GIVE US DIRECTION ON WHAT TO DO WITH LAMP
INSTALL ON 13.10.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Information type changed from Private Security to Public Security
** Also affects: ubuntu
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/1263071
Title:
All the above is on the schroot-1.6 git branch; 1.7 is on the master
branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153
Title:
[MIR] schroot (and lockdev)
To manage notifications about
have looked at adding one, but
doing this for C++ looks quite intimidating. I'll be happy to add one,
but might need a little assistance to do so. This will certanly become
more important for 1.7/1.8 which switches to using a shared library from
the existing static library.
Regards,
Roger
--
You
you would like changing or improving)? If not, this will
be released as 1.6.6-1 after further testing.
Thanks,
Roger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153
Title:
[MIR] schroot
Public bug reported:
safeboot mode necessary
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Note that current development (1.7.x releases, in experimental) have
dropped the lockdev dependency. And we're actively removing the lockdev
rdeps to allow lockdev removal for jessie. We also updated to dh9 and
cmake for building.
Regards,
Roger
--
You received this bug notification because
I think there are a number of bugs here.
The version I see is.
With Turn screen off when inactive set to 30 minutes and Suspend when
inactive for set to 1 hour. If I come back after an hour the screen has
turned off, but the computer has not suspended. When I wake up the
screen the dekstop has
Can you point me to other builds you want me to try, ideally as ppa
links like the above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer
I'm confused as to what the goal is. The drm-intel-nightly works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer work
To manage
This didn't work:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.7-saucy/
This did:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/
It would be ideal if you gave me a list of urls like above in preferred
testing order
--
You received this bug notification because you are
I installed 3.12 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.12-saucy/
It failed to boot. With normal boot there was no further progress after
ramdisk loading. In recovery mode the kernel said it failed to execute
/init but gave no further details.
I am now trying
The drm-nightly from previous comment works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no longer work
To manage notifications about this bug go
Booting the raring kernel (3.8.0-33) under saucy results in all 3
monitors working correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression - three monitors no
It appears to be ok now in 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1121447
Title:
Evince segfaults when run from command line
To manage notifications about this bug go to:
Is there a separate Seamonkey version of this bug? In Seamonkey 2.21 on
Win7 none of the reply, forward or show source commands seem to work for
a message/rfc822 attachment to a Mailman mailing list digest which has
been opened by double clicking on it. Right clicking on the attachment
in the
The same problem exists even for files with diffrent but similar names
because Filenames are truncated and there is no way to see the full
Filename in the dash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
for me, although
it does appear to have worked for others.
From my point of view this bug is resolved upon upgrade to Ubuntu 13.10.
Roger Tolhurst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1133658
Which driver did you get working in the end? My experience was having 3
monitors work fine in raring 13.04, until the driver that is in Saucy
13.10 at which point it started pulling the only two monitors at a
time stunt. Bug 1242180
--
You received this bug notification because you are a
xrandr output running command line from comment 2. Raring:
crtc 0:1920x1200 60.0 +1920+0 DP2
crtc 1:1920x1080 60.0 +3840+0 HDMI1
crtc 2:1920x1080 60.0 +0+0 HDMI3
Saucy livecd:
xrandr: Configure crtc 2 failed
crtc 0:1920x1080 60.0 +3840+0 HDMI1
crtc 1:1920x1080
@RichardNeill - already did all that as mentioned in comment 4 which
also has the advantage of working on the livecd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242180
Title:
saucy regression
For me, dragdrop (moving items between categories) is also not working.
On starting, stderr gives:
(alacarte:9493): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure:
assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL'
failed
(alacarte:9493): Gtk-CRITICAL **:
Ok, some investigation reveals that dragdrop was dropped in 12.10. I had 12.04
running prior, with menus already setup, and upgraded later thus not noticing
this. So this would be a separate issue.
Besides that, i checked that alacarte actually creates at least item- and
folder-entries in
xinput list-props 11 shows Synaptics Edge Scrolling 0,0,0
somehow xorg.conf is changed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1241220
Title:
after upgrade my touchpad scrolling did not work
** Attachment added: xorg log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884152/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The failures to set occur using the graphical tool from system settings,
as well as the xrandr command line
xrandr --output DP2 --primary --auto --output HDMI3 --auto --left-of DP2
--output HDMI1 --auto --right-of DP2
** Attachment added: xrandr output
Public bug reported:
I've just upgraded from raring. There I had 3 monitors attached to my
Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two
monitors are identical flanking my centre displayport monitor.)
In saucy I can get any two monitors working, and any attempt to get
I also ran xorg-edgers-live-test as described in
https://wiki.ubuntu.com/XorgOnTheEdge and that didn't help. Restored
from my backup and everything works fine.
(xorg-edgers-live-test also needs updating - it tries to restart gdm
when it should be restarting lightdm)
** Attachment added: xrandr
** Attachment added: xorg log from raring where everything works fine
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884309/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just upgraded to 13.10 and am getting this on every login. It was
working fine on 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/632066
Title:
systray.py crashed with SIGSEGV in
Public bug reported:
no problems before upgrade on I believe 13.06. after upgrade and
reboot, didn't work. went to system settings mouse and touchpad,
everything looked OK. enabled natural scrolling and it still did not
work.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package:
Public bug reported:
Dist: Ubuntu 10.12
roger@roger-Aspire-5920:~$ ubuntu-bug linux
roger@roger-Aspire-5920:~$ cat /proc/version_signature version.log
roger@roger-Aspire-5920:~$ cat /proc/version_signature version.log
roger@roger-Aspire-5920:~$ sudo lspci-vnvn lspci-vnvn.log
[sudo] password
Exact same situation. Also with
http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu
http://ppa.launchpad.net/bumblebee/stable/ubuntu
in the sources
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218547
I am suffering from the same bug using a P502 also named Sager NP9150 (P150EM
Barebone)
with an AMD 7970m and an Intel igpu.
As I workaround i use a small script I have attached. Placed in /etc/pm/sleep.d
it seems to work for the moment.
Dont forget to make it executable.
I have no problems
Public bug reported:
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-53.55-lowlatency-pae 3.2.50
Uname: Linux 3.2.0-53-lowlatency-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
--not being able to do anthing to fix it myself was
quite frustrating.
Regards,
Roger
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339
Title:
10mount: umount: /CHROOT/dev: device is busy
I can reproduce the following symptoms:
- Windows (Super_L) key doesn't bring up the menu.
- Right-clicking on the menu button does nothing.
- Search works, but I can't press Enter to select the result. It does nothing.
- Mouseover the categories does nothing.
Disabling places and bookmarks fixes
I have no idea on the other Ubuntu versions as I only use 13.04. I did
use awstats on the past, but had been using Google Analytics for over a
year. In the comments linked from the report there is another user
reporting only coming across the problem on upgrade to 13.04.
I didn't provide a
I have no idea on the other Ubuntu versions as I only use 13.04. I did
use awstats on the past, but had been using Google Analytics for over a
year. In the comments linked from the report there is another user
reporting only coming across the problem on upgrade to 13.04.
I didn't provide a
501 - 600 of 2231 matches
Mail list logo
