attachment is generated by the nvidia-bug-reporting tool, which collects
many logs
** Attachment added: "nvidia-gathered logs"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1764089/+attachment/5116362/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you
Chromium/Chrome has patched this from current 66 betas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755182
Title:
Horrendous latency in Chrome
To manage notifications about this bug go to:
https:
PS prime sync enabling is via modprobe.d file, the method I have always
used. I actually have the latest build from the ppa, so technically the
bug should be report there but it also existed yesterday when the
version of the driver was the same as currently in bionic.
--
You received this bug not
prime sync is still not working for me. It goes not enable and can not be
enabled
I have a quadro 1000m on a thinkpad w520. Attached is the output from
nvidia-bug-report.sh
** Attachment added: "nvidia-bug-report.log.gz"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+
Public bug reported:
1) to save power, sudo prime-select intel
and boot in hybrid graphics
This is the only way I know to get the nvidia card off which is the only reason
I boot like this
This still works, although it is really slow.
2) to go back to multi-monitors, reboot, at bios turn on dis
I add to my report that it is also still broken on my Thinkpad P50, with the
390.48 driver (I just updated everything).
This bug needs to be reopened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
Right now, it seems that prime-select intel makes sure the nvidia driver is not
loaded, as nvidia-settings reports.
But my power consumption is > 20W.
cat /proc/acpi/bbswitch reports the card is still on.
If bbswitch and powertop are reliable, then the nvidia card is still
However, I do not have this problem on my Thinkpad P50. The nvidia card
is definitely turned off when in hybrid graphics after prime-select
intel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765363
I didn't note the lack of a driver version. Thanks, I will check that.
On Thu, 19 Apr. 2018, 22:26 Doug McMahon, <1752...@bugs.launchpad.net>
wrote:
> @tim
> not sure if the ppa 390 driver was patched
> Works fine here either thru a conf using -
> options nvidia_drm modeset=1
> or a grub option
Thanks Doug. On the W520, prime sync does work if you change the config.
This was an upgraded system so it had the old style config (in /etc/modprobe.d)
and I missed the change.
gdm3 works for me too on this one, although no external monitor attempted (but
nvidia output to the laptop panel is de
I re-confirm this. Stock 18.04 has no graphics in pure nvidia mode (on a
Thinkpad W520 in discrete graphics).
lightdm works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
gdm3, hybri
Public bug reported:
I don't know how to replicate this bug yet, I will update if I learn more.
Several times as I test prime-select on my Thinkpad P50, I have ended up in
situations where the laptop will not start graphics. This always happens if you
leave the laptop in prime-select intel and
Public bug reported:
The new prime-select has some problems.
It is very slow to switch, since it does initramfs -u each time
It leaves my two optimus laptops without graphics if you leave it in
prime-select intel but boot with discrete nvidia. Previously this would load
nvidia drivers.
These ar
Hi Ryan, my solution uses bbswitch to turn off the card, which is what Ubuntu
used before 18.04. If it works for your hardware in 16.04 (up to and including
17.10) it will work in 18.04. Also if it was working and then stopped working,
it must be something you did.
If you'd like support with
Matthieu's code is the best solution I've seen, as long as you are ok with
lightdm.
The multi-dispatch aspects of the new module are a good simplification,
Matthieu's approach looks like it's now easy to switch between intel and hybrid
modes; he just blacklists modules.
Dear maintainers, it see
I've made a few tweaks which you can see here
https://github.com/timrichardson/Prime-Ubuntu-18.04
it now works between reboots. I should do a fresh install to make sure
it works without action. For example, I've made a note that after
install I did
sudo systemctl enable prime-socket
the problem
Public bug reported:
I have no further details to provide.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.39
uBlock fixes it for me and others ... But there should be some user
control
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs a
If you use gparted to disable your existing EFI partition prior to install, and
if you have followed the advice to create a gpt partition table and an EFI
partition, you can work around it.
After the install, use gparted to reflag your internal EFI partition.
This worked for me with Ubuntu 18.0
Public bug reported:
Launch sysinfo as root or user, don't matter
After it launches, click the system icon for information about the system.
The application crashes.
root@w520:~# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
root@w520:~#
root@w520:~# apt-cache polic
the revised package does not seem to be in Xenial repositories (yet?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575182
Title:
sysinfo crashes on ubuntu 16.04 (since upgrade)
To manage notifica
crete nvidia (not
> optimus)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
gdm3 and nvidia binary drivers don't work together yet. Maybe 18.04 although
there's not much evidence that anyone who knows how to fix this problem is
working on it.
This problem has emerged since the default Ubuntu session now uses gdm3 (as of
17.10) but standard gnome users on all recent dis
And also note that modeset=1 is not designed to activate wayland. It is
necessary to use the Prime Synchonization feature of the new nvidia
drivers, which is actually a feature of X 1.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update & simplication.
This bug affects 17.10 & 17.04 with the current LTS support nvidia drivers.
This bug affects both my laptops with nvidia hardware.
External monitors are not necessary to reproduce.
Reproduction is simple.
1. Activate the nvidia hardware using discrete mode. Therefore no int
It is also broken on a ThinkPad W520, which is much older hardware
(although still supported by current nvidia drivers). The Nvidia driver,
gdm3, gnome (or gnome ubuntu) and modeset=1 is broken. Replace gdm3 with
lightdm, and everything works.
--
You received this bug notification because you are
On the newer machine, the P50, I reinstalled 17.10 ubuntu yesterday,
with pre-release packages enabled. It is using gdm3. It works, even with
nvidia modeset=1 and external monitors. It is not obvious to me which
updated packages have fixed this, since I also tried pre-release on the
broken install.
Sorry, that was premature. I had not enabled modeset=1 properly.
After doing that
a) in Optimus mode, only the laptop display works. The nvidia settings control
panel opens, but it detects no screens.
b) in discrete nvidia BIOS mode, gdm is stuck in a greeter loop when trying to
start a Gmome or
exists in 4.12 and 4.13 in the 17.10 repositories.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687910
Title:
[Lenovo W520] Linux Freezing Issue At Boot
To manage notifications about this bug go
gt;
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706474
Title
ification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/g
> https://bugs.launchpad.net/bugs/1714881
>
> Title:
> no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
> optimus)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gdm/+bug/1714881/+subscriptions
>
--
Tim Richardso
#22 worked for me, after logout/login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620806
Title:
gedit edit window is transparent when using Ambiance and Radiance
themes
To manage notificatio
Ciro, you have reported "works for me" but you have not confirmed that
you are actually trying to reproduce the bug. The problem occurs when
using modeset=1. You do not mentioned that here or in your related
answer on askubuntu
If you are not using modeset=1, which is essential for people using
Op
Follow the upstream bug.perhaps you can help with testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290787
Title:
[TOSHIBA Satellite U400] suspend/resume failure
To manage notifications about
13.04 is ok for me.
On 09/11/2013 10:05 pm, "Andrejs Hanins" wrote:
> Hi all, sorry for bothering, but I'm upgraded to latest Ubuntu 13.10 and
> the bug is still there, despite the fact fix was available few months ago.
> Is it expected situation?
> Thanks.
>
> --
> You received this bug notifica
this is a kernel bug. git bisect completed and reported on the upstream
report https://bugs.freedesktop.org/show_bug.cgi?id=76520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290787
Title:
[TOSHIB
this is a kernel bug
** Package changed: lightdm (Ubuntu) => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290787
Title:
[TOSHIBA Satellite U400] suspend/resume failure
To man
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289721
Title:
[TOSHIBA Satellite U400] suspend/resume failure
To manage notifications about this bug go to
** Attachment added: "nvidia-bug-report"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921327/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
ubuntu 17.04 with gnome desktop.
The laptop is a Thinkpad p50 with a quadro M1000M.
To get this bug I am using the hybrid graphics mode.
This problem occurs with 375.82 and also with the new 384 driver.
When using gdm3 and
options nvidia_375_drm modeset=1
the greeter only s
** Attachment added: "xrandr output"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+attachment/4921331/+files/xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706474
Title:
I have the same symptoms as this bug with 17.04 and the new 375.82
driver if I am use modesetting with gdm. With lightdm it works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559576
Title:
U
launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
Tim Richardson
--
You received this
o the bug
> report.
> https://bugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
What's the bug report for hybrid systems? I can't get gdm working with
modeset=1 (aiming to get PRIME sync working). Is good in lightdm. There
are so many bug reports with similar symptoms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
*** This bug is a duplicate of bug 1705369 ***
https://bugs.launchpad.net/bugs/1705369
** This bug has been marked a duplicate of bug 1705369
Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop
with an Intel GPU)
--
You received this bug notification because you ar
For what it's worth, nvidia Optimus requires the integrated display to
be modeset=1, this is what you mean by "nomodeset would break laptops",
I assume. Should we be reporting this upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Maybe https://bugzilla.gnome.org/show_bug.cgi?id=784470
** Bug watch added: GNOME Bug Tracker #784470
https://bugzilla.gnome.org/show_bug.cgi?id=784470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
using Nvidia drivers (on a
> desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>
--
Tim Richardson
** Bug watch added: GNOME Bug Tracker #784470
https://bugzilla.gnome
ugs.launchpad.net/bugs/1706474
>
> Title:
> gdm3 nvidia modeset=1 is broken, external screens don't work
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706474/+subscriptions
>
--
Tim Richardson
--
You received th
17.10 repository.
On 28 August 2017 at 21:08, Tim Richardson
wrote:
> Thanks Doug, that bug report is exactly as the nvidia forum so you and I
> are doing the same thing.
>
> On 28 August 2017 at 02:41, Doug McMahon <1706...@bugs.launchpad.net>
> wrote:
>
>&
Public bug reported:
This is to track
https://bugzilla.gnome.org/show_bug.cgi?id=787207 " gdm & nvidia with modeset=1
causes loop, does not launch greeter "
I don't know if this is an nvidia bug or a gdm3 bug but it requires both
to reproduce.
[reply] [−] Description t...@tim-richardson.net [
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714881/+attachment/4943940/+files/Error_syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714881
Title
Daniel, with the latest 17.10 the nvidia problems are now more specific and
easier to reproduce.
Neither of my Thinkpads gets to the login screen in discrete Nvidia mode iff
modeset=1 is used.
In hybrid graphics, the session starts, I suspect this is due to the
intel driver being available. If
As of the latest updates to gdm3, I still can't boot with my laptop when it's
in discrete mode (nvidia graphics only). Does not get to the greeter.
syslog is full of countless repetitions of "Stopping NVIDIA persistence
Daemon".
CPU must be high because the fan comes on. I've reported this but
Public bug reported:
Context:
17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia
driver.
ubuntu desktop (gnome shell), fresh install
ThinkPad W520 in Nvidia Optimus bios mode.
Nvidia profile.
Result:
no external monitors are detected.
xrandr does not even list them as
** Summary changed:
- no gdm3 greeter with nvidia quadro and modeset=1
+ no gdm3 greeter with nvidia quadro and modeset=1, discrete nvidia (not
optimus)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I have a ThinkPad P50 and Prime sync is now working for me. I don't know
what change happened, sorry; it was two weeks since I did an update, and
it could be an updated kernel or updated xserver packages from Timo's
PPA. I have the 375 driver. And it works really well, it's marvellous
to behold no
I've been testing 1.19.x in 17.04 pre-release for a few weeks, hoping to
take advantage of the Nvidia PRIME synchronisation fix for laptops with
Optimus hybrid graphics. As of 1.19.3, PRIME sync works (with a modprobe
fix related to the nvidia driver). This is a huge improvement for nvidia
Optimus
"if dnsmasq's option "--dns-loop-detect" via DNSMASQ_OPTS in
/etc/default/dnsmasq."
this does not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Still a problem in 17.04. I don't see how to turn comment #21 into a
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282314
Title:
Evince cannot open HTTP link in Google Chrome or chromium-brows
It is not fixed for me. I have proposed-updates and the network-manager
version is 1.2.0-0ubuntu0.16.04.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578962
Title:
nm-applet crashed with SIGABRT
Didn't know it was a button. This works.
** Changed in: unity-control-center (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564890
Title:
additional us
I hvae reported this bug here, where I am adding information in response
to questions:
https://bugzilla.gnome.org/show_bug.cgi?id=765830
** Bug watch added: GNOME Bug Tracker #765830
https://bugzilla.gnome.org/show_bug.cgi?id=765830
--
You received this bug notification because you are a me
Public bug reported:
i have an openvpn connection configured. i use network manager to
connect successfully. later i use nm to swap back to the wired
connection. network-manager crashes, the icon is gone. however, the
connection does change.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: n
(Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1576162
>
> Title:
> network-manager crashes when exiting a vpn connection
>
> To manage not
Public bug reported:
new install of 16.04
went to add a second admin user via the control center immediately after
install
the user can be created but password is not requested and the user is disabled.
i could not progress via the control panel.
i added a password from the shell.
correct: ne
The bug is fixed. No more assertion, no more crash.
A message informs me that the wired connection is now established.
Then the next message says that the "ethernet" connection is disconnected.
Despite that final message, the change from VPN to normal wired connection now
works fine.
--
You re
I have ubuntu 16.04 as a virtual box guest. If I suspend the system (ie,
close it and save state) the mouse pointer is not visible when resuming.
The switch to terminal and back to X does not work, unfortunately. I
don't recall this happening in 15.10. The bug occurs with virtual box
5.0.16 through
the patch for this has been added to stable kernels 3.15 and 3.14 so I
hope it gets picked up by Ubuntu soon.
"""
This is a note to let you know that I've just added the patch titled
drm/i915: Avoid div-by-zero when pixel_multiplier is zero
to the 3.15-stable tree which can be found at:
The good news is that just an hour ago the Intel engineer and I finished
testing the fix, so it will go into the kernel soon (I don't know when).
Ubuntu kernel developers will pick it up I expect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
I run ubuntu-bug linux and I get a message that it is sending the
information, but then firefox opens me in a new bug report which again
asks me to run ubuntu-bug linux. I don't know what to do.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-gener
Public bug reported:
After resuming the hard drive and fan flash. But there is no screen.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-15-generic 3.13.0-15.35
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic i686
Annotation
Public bug reported:
suspend fails, does not resume
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-16-generic 3.13.0-16.36
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic i686
Annotation: This occured during a previous suspe
Public bug reported:
does not resume (no backlight on LCD panel, for example)
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
Annotation: This occur
3.13.6-031306-generic
kernel-bug-exists-upstream
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290787
Title:
[TOSHIBA Satellite U400] suspend/resume fail
with 3.13.6-031306-generic the bug still exists.
Now I'll check the latest 3.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289721
Title:
[TOSHIBA Satellite U400] suspend/resume failure
To manag
bug exists in 3.14.0-031400rc6-generic
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289721
Title:
[TOSHIBA Satellite U400] suspend/resume failure
To ma
My bug message is bad. The bug reporting indicates that it is actually a
kernel panic.
Please close this bug. automatic bug reporting was fixed when I changed the
login user to belong to group sudo.
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289721
and
https://bugs.launchpad.net/ubu
upstream report
https://bugs.freedesktop.org/show_bug.cgi?id=76520
** Bug watch added: freedesktop.org Bugzilla #76520
https://bugs.freedesktop.org/show_bug.cgi?id=76520
** Tags added: kernel-bug-reported-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Note: it is not an upstream bug.
I can not reproduce it like so:
go to terminal
sudo service lightdm stop
pm-suspend
this always works, with 3.11.10, 3.12.14, 3.13.6 and 3.14 rc7
However, when lightdm is running, does not resume.
** Tags removed: kernel-bug-reported-upstream
--
You receive
testing reveals that the bug is linked to lightdm
It is not reproducible when lightdm is not running. When lightdm is running, a
wide range of kernels show the resume fail. These kernels do not fail resume
when lightdm is not running
** Description changed:
does not resume (no backlight on LC
Public bug reported:
Hardware is
*-display:0
description: VGA compatible controller
product: Mobile GM965/GL960 Integrated Graphics Controller
(primary)
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-desktop-tests/+bug/1169984/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I have this problem with 14.04 but I will report a new bug since the
version is so much later
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980025
Title:
No option to save new OpenVPN connections
T
Public bug reported:
This is 14.04 32 bit intel.
I have installed OpenVPN access server on another machine. It is configured
with username and password security.
By logging in to it, a configuration file can be downloaded.
I want to set up a VPN network connection for this.
So I go to the conn
Public bug reported:
kubuntu 11.10
I;ve added a second user to the system via the kdeadmin interface.
When the user attempts to log on, they are presented with a dialog requiring an
immediate password change,although this is not requested when the user is
created.
The dialog entry to accept the
I get this on kubuntu 12.04 and Ubuntu 12.04
To reproduce, install inkscape and python-uniconvertor
1) start inkscape and make a simple document
2) save as type sk1 vector graphics files (.sk1)
The save will fail with the error message
UniConvertor failed:
Cannot load plugin module sk1saver
Trac
For me, this happens on a 64 bit Ubuntu 12.04 and a 32 bit Kubuntu 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/998705
Title:
package python-uniconvertor 1.1.4-1ubuntu1 failed to install/upgr
In my haste to find any bug on this package, I realise that I have reported a
different bug.
However, the conclusion is pretty similar. The packaging of python-uniconvertor
in 12.04 is broken.
Part of the installed files seem to refer to a library which belongs to a
different version.
The erro
This package is broken.
It's fairly easy to install the latest version from the sk1 website.
see
http://sk1project.org/forum/viewthread.php?thread_id=472&pid=1108#post_1108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Public bug reported:
I have an ubuntu 12.04 LTS server. I've set up proxy server on apache2, on port
443.
The server serves SSL web pages, and I can ssh to the server from a remote
shell. I can connect to ssh with a password.
I've set up proxytunnel so I can ssh to it from anywhere. But it's fai
I have requested help already via the forums, but didn't get an answer.
I guess it's an Apache problem because the error is a socket read error, but I
don't know enough to test this. I actually don't know what a socket read error
means. There one another reports of similar problems on RedHat, whe
I made a 13.04 live USB, updated it which means in my case 32 bit 3.0.19.
Booted from this, the Dragonfly worked fine. However, the installed Ubuntu
currently uses the mainline kernel 3.8.8 and the dragonfly doesn't work as
described here.
3.0.19 isn't an option on this machine since it is a me
Tim Richardson wrote:
> I made a13.04 live USB, updated it which means in my case 32 bit3.0.19.
Correct is: 3.8.0-19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Co
I confirmed this report since I seem to have the same problem caused by
the same kernel upgrade, although my sound hardware is integrated Intel,
not nvidia
http://ubuntuforums.org/showthread.php?t=2136303
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
rolling back to 3.8.0-17 worked for me which confirms which kernel
update introduced the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169761
Title:
3.8.0-18 Kernel causes HDMI Audio to st
Probably not interesting, but my Dragonfly USB async DAC has this
problem as well in 13.04 (I just upgraded today, from 12.10 which worked
perfectly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/11361
With a Dragonfly USB DAC on 13.04 development 3.8.0-15-generic (64 bit)
I get this bug.
Plugging it into an arch machine with 3.8.4 32 bit, there is no problem with my
DAC.
So if it's upstream, it was fixed between 3.8.0 and 3.8.4
The DAC was working well with 64 bit 12.10. I upgraded to 13.04
201 - 300 of 393 matches
Mail list logo
