Image showing window much bigger than needed with more than 90% blank
area.
Obtained with
zenity --info --text="$( for (( A=0; $A<20; A=$A+1 )) ; do echo -n
'lorem ipsum ' ; done )" &
** Attachment added: "Image showing window much bigger than needed with more
than 90% blank area."
https:/
Public bug reported:
* Context
Simple execution of zenity
* Summary
zenity window opens too big.
The text appears on top but most of the window area is just empty.
* How to reproduce
Just type this :
zenity --info --text="$( for (( A=0; $A<20; A=$A+1 )) ; do echo -n
'lorem ipsum ' ; done )"
Thank you asl97.
It seems indeed to be bug #1206760 (I tried to find before posting but
did not find that one).
Workaround is effective (well, in situations when it is acceptable, as
in all workarounds).
--
You received this bug notification because you are a member of Desktop
Packages, which i
It seems three bugs are about the same issue : #1087520 #1206760 and
#1273981. Some have insightful content.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1273981
Title:
zenity window
It seems three bugs are about the same issue : #1087520 #1206760 and
#1273981. Some have insightful content.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1206760
Title:
Zenity text w
It seems three bugs are about the same issue : #1087520 #1206760 and
#1273981. Some have insightful content.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1087520
Title:
Zenity window
Public bug reported:
While trying to get a proper display without high heat on an Optimus laptop, I
installed then uninstalled nvidia driver.
On uninstalling, apt complained about nvidia-persistenced that was running, and
indeed it was true.
Manually killing the process allowed to finally uninst
Public bug reported:
# Context
Using emacs in markdown-mode.
# Affected features
* search-and-replace misses some occurrences
* sometimes downcase-word and capitalize-word operate on a wrong region
(correct size but off by several characters)
* sometimes dabbrev-expand is affected, too, in a s
Package: emacs-goodies-el 35.2ubuntu2 contains markdown-mode.el
unmodified from upstream version: 1.8.1 as can be verified :
$ wget -q http://jblevins.org/projects/markdown-mode/markdown-mode.el -O - |
diff -sq /usr/share/emacs/site-lisp/emacs-goodies-el/markdown-mode.el -
Files /usr/share/emacs/
Summary : interestingly, in a bare X session, xev does not react to
those hotkeys, while it reacts to other. Does it mean the problem lies
at X level ?
## General test
To isolate the problem, I logged in with an empty account running
OpenBox only (no full desktop environment) and ran xev.
Here i
One more specific information : in bare OpenBox X session, none of these
keys have a visible effect handled by Ubuntu, except XF86WLAN.
Also, this laptop was sold with Windows, and there all function keys
work, including the brightness keys.
## kernel-level showkey test
I've tried https://wiki.u
** Summary changed:
- Partially broken brightness hotkey handling.
+ Brightness hotkeys not seen by kernel on Asus n55s, other hotkeys ok.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.l
Short version:
* upstream bug existed, now fixed in git but not released
* in the meantime use version from git
* bug should propagate to Ubuntu package eventually
Long version:
I now use version from today's git and confirm it fixes the bug.
>From upstream author Jason Blevins:
> Thank you ver
Perhaps the crash that sometimes happens to emacs using markdown-mode 1.8.1
*is* itself a bug in emacs.
I won't open a launchpad bug for that crash, but if you feel there should be
one, please open one.
--
You received this bug notification because you are a member of Desktop
Packages, which is
According to
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html
moving ~/.fonts.conf to ~/.config/fontconfig/fonts.conf is right.
Adam, any reference about using ~/.fontconfig/fonts.conf ?
http://freedesktop.org/software/fontconfig/fontconfig-user.html does not
confirm.
--
On my Ubuntu 12.10:
~/.fontconfig is ignored
~/.config/fontconfig (as expected) works
which is not surprising as /etc/fonts/conf.d/50-user.conf contains :
fontconfig/conf.d
fontconfig/fonts.conf
but does not mention ~/.fontconfig .
--
You received this bug notification because
Quantal shipped with "old" util-linux 2.20.1-5.1ubuntu2.
This bug is serious as it can render the system unbootable, see
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1012081/comments/5
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1012081/comments/6
Human user does not e
Public bug reported:
Bug reported with xdiagnose.
# Summary
On installing Ubuntu 13.10 or 14.04 on a NTA3500 nettop with a VGA
monitor HP vs19e (native resolution 1280x1024), a resolution of 1024x768
is obtained.
The bug is not that the correct resolution cannot be obtained at all
(there's a wo
Hello all,
Similar problem here.
## Problem description
Lubuntu 14.04 installed from beta (or daily).
Selected french keyboard.
Keyboard ok before login, every time (after boot or logout).
Logging in using lubuntu-notebook session.
After login, us keyboard is active instead of french.
## Wor
Whoops, my message was posted too early. Continuing.
## Warning for lubuntu users.
It appears that ibus is required by lubuntu-desktop, which makes the
problem only more present and increases impact of the workaround.
Indeed removal of ibus removes lubuntu-desktop which in turn makes some
other
@Christopher, yes, you're right to ask Jaime to make a separate bug
report. One reason is hardware is different. Another reason is this bug
report was for an older release.
> Christopher M. Penalver (penalvch) wrote on 2014-01-09: #7
> gouri, this bug was reported a while ag
Also suffering this UI bug of sort, also on Ubuntu 12.10.
On my machine, four of the eight partitions are displayed with a star.
The right-pointer triangle appears when the partition is mounted, so
it's probably meant as a "media play" metaphor.
The star usually means "new" (irrelevant here), or
Just tried xubuntu 13.10 on the same laptop, keeping 12.10 on its partition to
boot on one or another as will.
Xubuntu 13.10 is freshly installed, not much customized but updates applied and
rebooted.
Kernel is 3.11.0-12-generic .
lsb_release -rd
Description:Ubuntu 13.10
Release:13
*** This bug is a duplicate of bug 1075923 ***
https://bugs.launchpad.net/bugs/1075923
I'm questioning the duplicate status of this bug.
I experienced exactly the symptoms described in the present bug-report
#1079246, that is reading from a gvfs-mounted directory. Whatever the
way to read (na
Hello,
On Ubuntu 13.10 (fresh install not upgrade) I observed that subwoofer yielded
no sound.
So I tested two fixes separately, changes from vanilla configuration are
indicated with "-->".
1. Post #8: Setting the pin configuration default to 0x99130112 for pin 0x16
--> Subwoofer plays sound, h
@langdalep wrote "You can't have two MTP clients talking to one device
at the same time."
What should be done, then ?
If I understand correctly, gvfs can multiplex calls from different
clients. So it might be a good idea to have it the only one to talk to
the MTP server. If so, rhythmbox could/sh
Hello simionbcn.
Thank you for your participation. Can you elaborate ? Several setups
were discussed, we can't guess what is yours.
What is your filesystem setup ? Your version of Ubuntu, of involved packages ?
What steps have you performed ?
Such information helps a lot.
Thanks.
--
You recei
Thank you simonbcn for these interesting additions (not saying I can do
anything about it, but a nautilus developer may pick that as valuable
hints about what's wrong).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
ht
The error message:
* is reproducible always,
* on trusty
* with zenity, abiword, gitg, gnome-calculator, probably with other or even all
gtk3-apps, too. I have tested only a handful and all exhibit this behavior.
Zenity is mentioned in bug #1326099 .
For example:
** (zenity:10455): WARNING **:
> Sorry for not answering again. Are there any news on this issue?
No news. As written above, I provided users a workaround with a
.xsession. That workaround was so effective that I even forgot this bug.
> Did you already upgrade to 14.04 or do you plan to do so?
It is planned and we already kno
Public bug reported:
# Context
On a Ubuntu 12.04 machine used by several users (two main users),
Thunderbird has been used for years on various WiFi networks. Each user
has his Unix account, one thunderbird profile, using IMAP server. Users
don't connect to same e-mail provider.
Yesterday evenin
When debugging it's sometime useful to have two similar situations, one
that works and one that fails.
We have that here.
Two machines :
* same brand (Asus) but not same model
* affected one is Ubuntu 12.04, working one is Ubuntu 14.04
* same WiFi network
* same Thunderbird version (from their r
It was simple enough to create a new profile from scratch for the affected
user.
Now thunderbird works.
So, something was broken in that user's profile.
If that can be two cents to encourage Mozilla to make a "reset profile"
feature like they did for Firefox, that would probably make things up.
Hello,
The user requested to get back their parameters, like identities, local
mail folders, etc.
I diffed the pref.js between old and new account and was surprised to
see that mail.root.imap references a non-existent directory.
It should have been
user_pref("mail.root.imap",
"/home/affecteduse
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/979959
Title:
"gnome-control-center display" crashes if no RANDR extension
Status in “gno
Thank you for submitting this bug.
Can you please read http://ubuntuforums.org/showthread.php?t=1996729 and
tell if, as written there, "the user does not have permission to access
to the root of the partition that is mounted" ?
Then please update this bug accordingly.
Thank you.
--
You receive
Sudo is not always enough (for example, autofs or networked filesystems).
See also bug #1035843 .
But even when you fix that manually you run into bug #594674 .
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https:/
@Sebastien Bacher (@seb128)
> @larson.erid.d: not sure it's really a "high-priority bug", such bind
mount setups are not common. Could you tell us a bit more of cases where
it's a concrete issue
Sure. This also happens on NFS mounts, which is more widespread than
--bind.
> and maybe read https:
Bug observed here before and confirmed again just now. Did not happen in
older releases of Ubuntu.
Interestingly enough, just tested, the "F10 pressed" event is indeed
sent to the terminal-based program. Tested with midnight commander (asks
to quit). Type "cat" then press F9 then F10. Both escape
### Confirmed here.
### Cause
Default angle measure is degrees but user does not know.
### Explanation of value obtained
Mathematically,
cos(pi degrees)=cos(pi * pi / 180 radians)=0.99849715
sin (pi degrees)=sin (pi * pi / 180 radians)=0.054803665.
but it is not what the user expects.
### Comp
You computation :
(2*2/5) =4/5=0.8
So gcalctool is correct.
Did you mean (2+2/5) instead ?
(2+2/5)=2.4
So gcalctool is correct again.
Marking invalid. Please reopen or comment if this is incorrect.
--
You received this bug notification because you are a member of Desktop
Packages, which is
gcalctool did what user asked.
** Changed in: gcalctool (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gcalctool in Ubuntu.
https://bugs.launchpad.net/bugs/996440
Title:
Getting invalid value wh
## Thanks @vdrok
> automatically lock the session - when the screensaver is activated
> delay locking after screensaver for - 5 seconds
> lock screen when system is going to sleep - checked
Hmm, on my system the delay was set to something small (perhaps even 0).
## Thanks @mag3sh
> From further
Still observed here.
This floods systemd's log, around 10 messages per second.
At first glance, the commit mentioned above seem relevant.
Even if a proper fix takes time to be incorporated, I'd be happy with a
workaround, but am clueless where to start man gvfds-metadata offers no
relevant optio
The bug is still triggered (not always) by suspend-to-ram then wake-up.
This make a frustrating user experience since the most affordable
workaround is to close the session the reopen it when bug occurs. Since
many applications are defaced (see screenshots), the user cannot
properly check if thei
Thank you Nuno for reporting the trouble you observed. I'm the one who
posted this very bug report where you added your comment.
I can understand your frustration. I'm frustrated too. I'm using open-
source nouveau driver instead and it has problems, too cf.
https://bugs.launchpad.net/ubuntu/+s
Thank you Nuno for reporting the trouble you observed. I'm the one who
posted this very bug report where you added your comment.
I can understand your frustration. I'm frustrated too. I'm using open-
source nouveau driver instead and it has problems, too cf.
https://bugs.launchpad.net/ubuntu/+s
Thank you Nuno for reporting the trouble you observed. I'm the one who
posted this very bug report where you added your comment.
I can understand your frustration. I'm frustrated too. I'm using open-
source nouveau driver instead and it has problems, too cf.
https://bugs.launchpad.net/ubuntu/+s
** Summary changed:
- Some glyphs drawn consistently wrong, bug comes and go
+ Suspend to ram causes some glyphs to draw consistently wrong or even appear
blank in gtk/gdk/pango/cairo apps. xterm/xmessage unaffected.
--
You received this bug notification because you are a member of Desktop
Pack
Summary: on reinstall on same CPU/motherboard/etc (only storage
changed), bug no longer observed.
Hello,
After observing problems on the main storage of the laptop where the bug
was observed, I bought a new storage and installed Ubuntu 16.04 from
scratch on the new storage but the same laptop.
S
Bug observed on Asus n551jk using nouveau driver with latest updates
applied.
Suspend not needed, locking is enough.
Ctrl-Alt-F1 then Ctrl-Alt-F7 works around, until next lock.
Thank you for your attention.
LC_ALL=C lshw -c video 2>/dev/null | grep configuration
configuration: driver=n
Regarding new bug, subscribed to
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1568604 . Will notify if I still observed this bug (1547077).
I don't understand why this bug no longer happens (which is good
anyway).
xserver-xorg-video-nouveau is still 1:1.0.12-1build2
P
Public bug reported:
# Context
Selecting nvidia driver using software-properties-gtk.
Install goes ok. No longer observing bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Hardware is Asus n551jk laptop. nvidia driver worked on same hardware
with Ubuntu 14.
Interestingly, thus bug started to reappear in its extreme form: a few
times in the past days, all letters disappeared in my xfce4-terminals.
Workaround was to close and reopen session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg
To add to my latest comment where I report that problem reappeared a few
times in recent days: same hardware, same usage pattern, on the very re-
installation of 16.04 that had the problem disappear (cf. #comment:77).
Software updates applied regularly since the last near-2-years. Nothing
salient w
Makes sense. Besides, I've been using XFCE for a long time now, so have
not had any visibility whether this bug still occurs with Gnome.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchp
I have a question for people experiencing this bug (yes, you included
:-).
Please:
* open xfce4-settings-manager,
* click icon "power manager",
* click tab "security",
* report what settings are there for when to "automatically lock the session",
"delay locking after screensaver for...", "lock
apport information
** Tags added: apport-collected has-workaround regression reproducible
ubuntu
** Description changed:
# Summary
* Some glyphs badly drawn at some moments.
* When happens, same glyph drawn on various windows shows same corruption.
* Problem comes and go.
# Conte
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585282/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585285/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585286/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585283/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585284/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585289/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585292/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585290/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "NonfreeKernelModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585291/+files/NonfreeKernelModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bu
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585294/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585293/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585295/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585296/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585299/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547077
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585300/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/15
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585288/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585297/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1547
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585287/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1547077/+attachment/4585298/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
Hello.
Suspending then resuming system seems to have some effect.
This morning, after resume from suspend (with session still open), all
text glyphs appeared blank on the lightdm screen.
I expected the session to be fully unusable, but surprisingly, the
session itself has had no problem at all s
@penalvch this goes into complications.
Actually, I've been using 16.04 and Intel driver because in 14.10, 15.04
and 15.10, all solutions (open-source nouveau driver, open-source intel
driver and proprietary nVidia driver) have had different problems (but
not this problem).
--
You received this
Public bug reported:
Installation of package was requested through Ubuntu driver selection
GUI.
Installation of package was motivated by investigation of bug 1547077.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bbswitch-dkms 0.8-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-7.22-gene
I'll try that BIOS test.
In the meantime I thought I'd try again nVidia proprietary driver.
Installation of package was requested through Ubuntu driver selection
GUI.
Resulted in 2 new bugs automatically notified and reported:
https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1552108
https
# Analysis: currently running kernel is actually purged
>From message in DpkgTerminalLog.txt:
> WARNING: missing /lib/modules/4.4.0-7-generic
I notice that I'm running
uname -a
Linux n551jk 4.4.0-7-generic #22-Ubuntu SMP Thu Feb 18 20:50:38 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Which packag
As requested by @penalvch, tested exact same hardware (nta3500 computer, hp
vs19e display) with today's daily live image downloaded from at
http://cdimage.ubuntu.com/daily-live/current/xenial-desktop-amd64.iso displayed
as "xenial-desktop-amd64.iso 04-Mar-2016 08:29 1.5G" with
md5sum 497d
Summary: trying proprietary nVidia driver as a workaround does not work.
I tried again to switch to nvidia-driver using GUI tool software-
properties-gtk
This caused again nvidia driver installation failure.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Last
Summary: trying proprietary nVidia driver as a workaround does not work.
I tried again to switch to nvidia-driver using GUI tool software-
properties-gtk
This caused again nvidia driver installation failure.
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1553554
Last
As requested by @penalvch, checked what the BIOS offers.
Answer: the BIOS does not offer to disable any intel or nividia chip.
In "Graphics Configuration", the BIOS only offers "DVMT Pre-Allocated"
with values 64M 128M 256M 512M, currently set to default 64M.
--
You received this bug notificati
Laptop stickers show: nVidia GeForce GTX 850M and lspci shows both
nVidia and Intel graphics.
I'm not quite sure if nouveau or intel driver is used.
egrep '(intel|nouveau)' -i Xorg.0.log -o | sort | uniq -c
62 intel
9 Intel
1 INTEL
12 nouveau
2 NOUVEAU
Can anyone tel
Hello Christopher @penalvch, you're the Jon Skeet of launchpad :-).
Honestly, I don't care about a backport.
The machine is currently running Debian actually. Had I needed Ubuntu, I
would have used 16.04 anyway.
So, I'll mark this as invalid as you request (I would not have
considered "invalid",
> gouri, Invalid fits better over Won't Fix as defined in
https://wiki.ubuntu.com/Bugs/Status .
Okay because of
> "What is the appropriate status if the original reporter later says the issue
> no longer exists but the related changelog does not note a fix?
>
>
Nouveau driver seems active according to dmesg.
[0.721176] nouveau :01:00.0: NVIDIA GM107 (117110a2)
[0.747014] nouveau :01:00.0: bios: version 82.07.2a.00.17
[0.856760] nouveau :01:00.0: fb: 4096 MiB DDR3
[0.856814] nouveau :01:00.0: priv: HUB0: 10ecc0 (1b
Still occurs with latest build
xserver-xorg-video-nouveau 1:1.0.12-1build2
*Bug is severely impacting for daily work.*
Strangely enough, video worked rather well with 14.10 and 15.04, we
mainly had trouble with NetworkManager there.
After using Ubuntu more than 10 years now (first was pr
After another failed attempt at installing nVidia driver through
software-properties-gtk here is another bug report
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1556960
So bugs happens every few days.
Hypothesis: bug happens when another X server is run. This happe
Public bug reported:
Context: Use emacs. Close graphical session.
Reproducible? Not tried.
Observed: emacs process eating as much as one CPU core as it could.
Expected: when session is closed, emacs process quits.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: emacs24 24.5+1-1ubuntu7
Pr
Sent SIGTERM (15). Observed: no effect.
Sent SIGHUP (1). Observed: process disappeared.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1557393
Title:
Runaway emacs24 process (100% of
Hello Christopher @penalvch.
> Could you please report this problem through the appropriate channel
by following the instructions verbatim at
http://nouveau.freedesktop.org/wiki/Bugs/ ?
I performed part of it. The situation passed the "TroubleShooting" step.
I checked on the bugzilla, visited #no
Unfortunately, the bug occurred again a few minutes ago.
This means that uninstalling light-locker and using xscreensaver instead
is not enough to prevent the bug from occurring.
AFAIK, doing so avoids light-locker creating possibly short-lived X
servers (for the purpose of asking password for un
On a USB audio adapter 0d8c:000c "C-Media Electronics, Inc. Audio
Adapter", I experience same problem as original report and comment #2.
Links at comment #3 no longer exist.
I can't correlate with comment #4 and #5. To me, original report and
comment #2 only mention an annoyance on a specific vo
On re-reading the original post (which is not very clear), I'm wondering
if it's same problem.
My problem is not on VLC-specific volume in pulseaudio (or any other
app), rather on the master volume (hardware-specific).
So, perhaps it's not the same problem.
Anyway, many things have probably chan
@gr-ubuntu-0 thanks for reporting, it looks like it's the same issue
indeed.
@gr-ubuntu-0 can you mark the bug as affecting you? It is important for
confirmation and prioritization.
Christopher wrote:
> #53 gouri, could you please provide the bugzilla number for the report
y
Thanks again @gr-ubuntu-0 . This is interesting. Indeed your XorgLog.txt
does not mention nouveau, only Intel.
My xorg.log mentions both.
Following https://askubuntu.com/questions/23238/how-can-i-find-what-
video-driver-is-in-use-on-my-system it looks like I'm really using
nouveau driver.
LC_ALL
1 - 100 of 135 matches
Mail list logo
