I upgraded to the 550 drives, which did seem to remove the simple-drm
piece from my logs, but the issue still occurs.
What looks like the Relevant part of the logs:
```
Sep 16 21:26:40 toothbrush /usr/libexec/gdm-x-session[2580]: (WW) NVIDIA(0):
Failed to request fliplock.
Sep 16 21:26:40 tooth
I've re-upgraded to 24.04 and this is still happening. I will look into
the posted workarounds and see if I can gather more information.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bug
/5123
And here's the case Jens Georg opened in response.
https://gitlab.gnome.org/GNOME/shotwell/-/commit/fa6884f73af83ccbc72b8fe0f7bc63a00630ee0b
Thank you!
Jon Redinger
jon_redin...@cfl.rr.com
To manage notifications about this bug go to:
https://bugs.launchpad.net/shotwell/+b
https://gitlab.gnome.org/GNOME/shotwell/-/issues/5123
And here's the case Jens Georg opened in response.
https://gitlab.gnome.org/GNOME/shotwell/-/commit/fa6884f73af83ccbc72b8fe0f7bc63a00630ee0b
Thank you!
Jon Redinger
jon_redin...@cfl.rr.com
** Affects: shotwell (Ubuntu)
Importance:
I'm not sure if this is the same exact bug, my problem just seems to
happen randomly not when necessarily when I close something, I'm still
trying to identify a reproducible cause. My problem seems more similar
to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
ubuntu-dock/+bug/20
Public bug reported:
I've written an AskUbuntu question about this:
https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075
Originally I thought it was gnome not respecting my setting to prevent
locking the screen after id
I've confirmed it does happen when just using super+arrow and no mouse
interaction. I still cannot get it to work reliably though.
My monitor setup looks roughly like this:
```
+--+
|2 | +--+
| | |1 |
+--+ | |
+--+ | |
|3 | |
I was able to get a screenshot of the issue. I edited the images to
remove sensitive information I was working with at the time, but the
point is that I was moving around windows (I forget if I was using
super+arrow or dragging to corners), and the issue happened. I'm still
not sure exactly how to
Public bug reported:
I've got a fresh install of the first 24.04 release, and I'm seeing
strange behavior related to super+arrow keys and the enhanced tiling.
I've disabled tiling popups and tiling groups, but I like the quad
blocks.
The issue is when I'm moving around windows, sometimes the oran
I can confirm the behaviour after a recent upgrade from mantic to noble
and has also been reported in https://discourse.ubuntu.com/t/noble-dev-
branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt-
install-work-but-apt-upgrade-fail/43979
Another oddity is, that I seem to have to typ
Public bug reported:
After upgrading mantic to noble, there are multiple SSH agents who are
independently trying to set SSH_AUTH_SOCK, none of which is successful.
1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to
/etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified)
This w
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1.
inxi -Fxz
System:
Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur)
Machine:
Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1
v: A3009DD
Same for me but some details that can be usefull to know :
- Using a workspace email = evrything is fine
- Using a personal google email = i have the endless loading problem
(for workspace i've used the "add a GOOGLE account" button)
Not too familiar with what .txt file to psot and how to do so..
Public bug reported:
I did the alt+f2 r workaround, but sent this bug report first. Hopefully
this system debugging information helps the team resolve the issue. It
happens frequently.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2
The SMB1 code should be entirely removed from the stack. It’s insecure and
deprecated everywhere.
On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net>
wrote:
> Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
> fixed? This is now over 4 years old.
>
> --
>
Update -- possibly resolved by upgrading to kubuntu 22.10.
I installed that and so far ... fingers crossed, no more black screens.
Jon
--
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
I have the same issue with a fresh install of kubuntu 22.04 LTS on an HP
820 G1. Random screen blackout -- machine can only be revived by a
reboot. The Windows operating system that was replaced by kubuntu worked
flawlessly (except that it was Windows, which is one hell of a flaw).
--
You receive
This is probably caused by something different than the described issue,
but I'm experiencing this symptom periodically on 22.04. I can still
move my mouse around, but I can't exit the overview. I can ssh into the
box, so it is some issue with gnome getting stuck. I submitted a report.
--
You rec
Public bug reported:
On an intermittent basis, Remmina will, if clipboard sync is on, drop to
an unusably low framerate after login to the remote machine. I have not
managed to fully determine the conditions under which this occurs: it
appears to happen or not happen consistently across a login se
** Description changed:
Reporting according to
https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4
Attaching:
xinput output
evtest output
xev output
xmodmap output
live videos of evtest and xev showing physical motion on trackpad
without cursor movement
Public bug reported:
Reporting according to
https://wiki.ubuntu.com/DebuggingTouchpadDetection , following section 4
Attaching:
xinput output
evtest output
xev output
xmodmap output
live videos of evtest and xev showing physical motion on trackpad
without cursor movement:
https://drive.google.co
Removal of the package 'sabily-gdm-themes' and rebooting had no effect
on my situation.
Daniel, perhaps you have some insight into this. What information I've found
in my internet search says that gdm/gdm3 defaults to Adwaita icon theme. I'm
looked for "how to configure" type articles
about gd
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and
rebooting had no effect on the issue. White square "mouse pointer" is
present on gdm login screen if /usr/share/icons/adwaita/cursors is
missing (renamed).
If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors
The reported problem is during login, not after successful login.
I don't think mutter configuration has any effect before graphical login.
Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's?
Two files affect the observed condition:
/usr/share/icons/Adwaita/cursors/left_ptr
/u
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8
Still having this problem. Very surprised it has lasted this long. In
any case, if it is fixed, will this change make it to the next LTS
update?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Same on Ubuntu 20.04 both GA and HWE kernel.
Sure, it just takes this command to find which package has it:
$ apt-file search libbd_mdraid.so.2
And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it.
Depends on packages I don't need, MOST don't need:
$ apt show libblockdev-mdra
Confirmed everything appears to be working. We can consider this closed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1930640
Title:
Error when using S3 multipart upload - TypeErr
After a little more digging, I believe part of my issue with the
boto3+s3 option was that I was still using the full URL rather than just
the bucket name, so rather than:
boto3+s3://BUCKET_NAME/folder
I was still using:
boto3+s3://s3-us-west-2.amazonaws.com/BUCKET_NAME/folder
So this appears to
No funny characters in the bucket name.
It's literally just alpha characters and dashes: labkey-artifactory-
backup
And the folder it drops into uses an underscore: artifactory_backup
I'll recheck that link. There were a few that I already saw, but were not
applicable to my situation.
--
You
I've tried using boto3+s3:// as well before and it was unsuccessful.
Swapping it out with this newer version of duplicity produced an error
regarding the HeadBucket operation.
See new failure below. I turned up the verbosity to 9 for this one.
Note: My company is using Duplicity 0.8.11 and Duply
Unfortunately, the same issue is coming up, even after installing the
requirements via pip.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/duplicity/backends/_boto_multi.py", line
223, in _upload
mp.upload_part_from_file(fd, offset + 1, cb=_upload_callback,
File "
I ran into the same issue, but upgrading to 0.8.19 didn't fix it.
I've put in a new bug for this:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1930640
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https
Public bug reported:
I followed the solution in
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971 (I was
running duplicity 0.8.11.1612-1 as well), but after upgrading to 0.8.19,
the problem still persists for me when trying to use S3 multipart
uploads.
Note: This problem doesn't ap
Public bug reported:
Disk Usage Analyzer no longer works at all; becomes unresponsive several
seconds after starting
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: baobab 3.34.0-1
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVer
** Description changed:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 344mm x 194mm
-1920x1080 59.93*+ 39.99
-1680x1050 59.93
-1280x1024 59.93
-
Public bug reported:
xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis)
344mm x 194mm
1920x1080 59.93*+ 39.99
1680x1050 59.93
1280x1024 59.93
1440x900 59.
Same issue for me as I'd like general notifications just not routed to
Gnome via the Evolution popup.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1805666
Title:
Evolu
Running Chromium Version 86.0.4240.111 (Official Build) snap (64-bit) on
Ubuntu 20.04 and I'm not seeing my policies enforced inside Chromium.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launch
Still doesn't work for me after all updates,and there are side
effects... Now every time I boot up, the Desktop's font is very small,
even there is no external monitor...if ALT + F2 -> R, then restore :(
libmutter-6-0:
Installed: 3.36.4-0ubuntu0.20.04.2
Candidate: 3.36.4-0ubuntu0.20.04.2
Ve
Will those changes be merged into the 20.04.1 release?
--
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/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
Status in gn
journalctl /usr/bin/gnome-shell -b0 -ef
** Attachment added: "journalctl2.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5391652/+files/journalctl2.log
--
You received this bug notification because you are a member of Desktop
Packages, which is s
@3v1n0
NVidi MX150 (440)
The updated package not work for me.
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5391651/+files/journalctl.log
--
You received this bug notification because you are a member of Deskt
Logically this seems to be correct. I’m not a samba developer, so I don’t
have direct insights to what is happening when. I don’t know much about
the samba discovery process.
The easy way to test this is startup FreeNAS in a VM because they disable
SMBv1 by default.
On Tue, Jun 30, 2020 at 2:05
No but when you use the automatic detection of smb services which I’m
guessing uses NetBios or something like that it won’t connect if SMBv1 is
disabled.
So simply navigating to Other Locations and clicking on the automatically
enumerated host names, the connection will completely fail if SMBv1 is
On a fresh install of 20.04, it seems my system is now sending crash
reports. From what I can tell this is a bug in gnome-shell instead of
gnome-screenshot as I initially thought. The most recent crash link as
of the time of writing is here:
https://errors.ubuntu.com/oops/8211fa26-ae79-11ea-a61b-fa
Thanks for pointing out those instructions. I wasn't entirely sure where
that stuff was.
Unfortunately, it seems that there's no useful crash logs in /var/crash,
and nothing is showing up online either. The best I can do is give you a
short video of the symptoms, in hopes that something can help.
Public bug reported:
When taking a screenshot, sometimes my whole GNOME desktop will crash.
It feels like about a quarter of the time.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screenshot 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-
Dear experts ,we're still waiting for the fix -(
--
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/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
Status in gnome-co
Affected as well:
Ubuntu 20.04 LTS
GeForce MX150
NVIDIA-Linux-x86_64-440.82.run
--
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/1870736
Title:
[nvidia] Screen scaling 125
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => jon grahaqm (skyking2630)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/938751
Title:
Images
ast but they seem to have been fixed before this
> bug report was raised.
>
OK, that is fine. Eventually, this system will get creaky
enough that I will have to update.
Just a case of inertia!
Thanks for looking into it, and glad that newer versions do
not have the problem.
Jon
--
URL is :
https://www.onsemi.com/pub/Collateral/FODM2705-D.pdf
I am still running 12.04 on some systems, I have too many
tricky packages installed to update until it is REALLY
necessary.
Thanks,
Jon
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.04
Release:19.04
Codename: disco
$ gnome-control-center -v
22:48:42.09
Public bug reported:
No border around windows, no resizing buttons (max, min, close). Windows
cannot be moved or resized. Alt+tab and Alt+F4 have no effect, but some
other keyboard shortcuts, e.g. ctrl+alt+T and ctrl+Q, seem to work ok.
Only closing a window changes focus; even clicking with mouse
I'm seeing this in Ubuntu 18.04 as well. I have 2 printers configured an
HP LaserJet p4015 and a Canon ImageRunner C5030.
kernel: [35100.990629] audit: type=1400 audit(1536755161.327:158):
apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd"
pid=15321 comm="cupsd" capability=12 capname
I have the same issue.
I am rotating syslog hourly - which isn't ideal but mitigates the
problem for now.
Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: == Stack trace for
context 0x55813e634330 ==
Sep 9 19:48:58 tsunami org.gnome.Shell.desktop[1920]: #0 0x7ffd6a265310 I
resource://
Public bug reported:
I am using an Ubuntu 18.04 Vagrant machine, which has had the ubuntu-
mate-desktop tasksel applied to it. I mount a filesystem from the
Virtualbox Host using this line in /etc/fstab:
HostHome /HostHome vboxsf
_netdev,uid=1000,gid=1000,dmask=0077,fmask=0177 0 0
With this
Yes, this bug should move to gnome-shell -- I'm using the default in
ubuntu-17.10, which is gnome-shell.
** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
h
Thanks for the questions
1) Removing the kernel parameter causes the same problem (plus, shutdown
doesn't work.)
2) I cannot take the graphics card out of the laptop, but I uninstalled
the nouveau package xserver-xorg-video-nouveau. This may have improved
things; see below!
3) This is on a fresh
Public bug reported:
I am running a fresh install of Ubuntu Desktop 17.10 on a Dell XPS 15 9560
laptop.
I'm using an external Thunderbolt dock to connect to wired Ethernet.
I have additionally installed openssh-server on the system.
When I boot the system as normal, NetworkManager ends up creati
Public bug reported:
I've installed ubuntu desktop 17.10 amd64 from scratch in UEFI mode on a Dell
XPS 15 9560 laptop.
This laptop comes with i915 built-in graphics, as well as an NVIDIA 1050 GPU,
but I am not trying to make the NVIDIA work yet, and have blacklisted nouveau.
I'm using xorg 1:7.
I believe this has been fixed in libsecret in
https://bugzilla.gnome.org/show_bug.cgi?id=778357.
** Bug watch added: GNOME Bug Tracker #778357
https://bugzilla.gnome.org/show_bug.cgi?id=778357
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
@sbierman & @md-5
I'm not sure of the relationship between the two files, but in addition to
`/usr/share/applications/gnome-terminal.desktop` you may also need to change
`/usr/share/applications/org.gnome.Terminal.desktop` similarly.
--
You received this bug notification because you are a membe
I already confirmed the "non-symmetric" behavior:
> the following padding does NOT cause the problem:
> padding: 1px 1px 1px 1px;
> The following padding DOES cause the problem:
> padding: 2px 1px 1px 1px;
Regarding scrollbars with un-filled space, I guess Linux will keep
sucking on the desktop f
Thanks for the pointer!
The window in the screen shot is taken with zero configured padding. The
green strip between the gray vim background and the orange scroll bar is
all ugly padding added by gnome-terminal.
It sounds from your description as if the real problem is in "vte" which is
used by
Output of "lshw"
** Attachment added: "lshw"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944297/+files/hw.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://b
output of "dpkg -l"
** Attachment added: "dpkg -l"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+attachment/4944298/+files/dpkg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
h
Thanks for your answer!
Yes, the ugly margin is there even when not maximizing the terminal and even
when not using a css override file. (I removed the css override so I can keep
working.)
I'm attaching a screen shot (the ugly border is only on the right side,
probably scroll bar related?)
Als
This affects me as well. I have trace information in the attached syslog.
Below are the outputs from:
* lsb_release -a
* apt-cache policy network-manager
* hwinfo --netcard
- jss
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:
Public bug reported:
Using Ubuntu 17.04, vim, in gnome-terminal. Default everythings from the
desktop install, default Theme. The only change is the default window
size in the settings -- I have it at 149x48. This bug happens even with
the default 80x24 window size. The font is the default (not ov
This looks very much like https://bugs.launchpad.net/bugs/1694129 which
I raised a week ago.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1692477
Title:
Thunderbird 52.1.1 no lo
u 3.13.0-119.166-generic 3.13.11-ckt39
Uname: Linux 3.13.0-119-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon2048 F pulseaudio
BuildID: 20170512195315
Cha
I raised this problem at https://askubuntu.com/q/904680/475088
For a temporary workaround, which at least gives you back the "New
Terminal" context menu item:
File "/usr/share/applications/gnome-terminal.desktop" includes line:
OnlyShowIn=GNOME;Unity7;
In 16.04 that line was:
OnlyShowIn=GNOME;
3.4.0-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
Thanks,
Jon
** Affects: evince (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evin
FIX:
Finally found a solution that does not require me to disable screen
blanking and turning my monitors off physically:
1. Run dconf-editor
2. org > gnome > settings-daemon > plugins > power
3. "Set to Default" on ALL keys (this sets GNOME to never blank the screen
since "sleep-inactive-ac-tim
Running Alt + F2 and then "r" to restart GNOME Shell helps speed up
everything again, because AFAIK it restarts gnome-settings-daemon, but
after that it still uses relatively much more RAM than after a reboot.
--
You received this bug notification because you are a member of Desktop
Packages, whi
Running Valgrind as described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1321995
...I get the content in the attachment, not very helpful it seems? Also
see my screenshot above.
Note: It should be noted that I run a dual monitor setup with one
monitor on DVI and another on HDMI. Saw a foru
See attachment. gnome-settings-daemon eating 65 % of my 8 GB RAM less
than 24 hours after a reboot.
** Attachment added: "Bug.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1585551/+attachment/4827646/+files/Bug.png
--
You received this bug notification because yo
Same her on Ubuntu GNOME 16.04 64-bit with GNOME 3 Team PPA. gnome-
settings-daemon can eat up my 8 GB RAM after time, and then desktop 3D
animations are very slow/choppy. Solution is to log out and in again.
--
You received this bug notification because you are a member of Desktop
Packages, whic
: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39
Uname: Linux 3.13.0-106-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0:
I've performed the upgrade from 12.04 to 14.04 over the Christmas break
which has restored all the repositories back to default (I was using the
PPA from Rolf's PPA to work round this) and can confirm it's all working
now. There's still the massive delay on the start of the initial scan
(as mention
Discussed with rbasak, with conclusion that this isn't high enough
priority to SRU; risky to change unless this is causing real production
issues. I'll attach my debdiff in case needing to resurrect at a later
time.
** Patch added: "libnl3_3.2.21-1ubuntu4.debdiff"
https://bugs.launchpad.net/
Public bug reported:
Hi
debian/rules only supports two values for DEB_VENDOR: Debian and Ubuntu.
As derivative distributions put other values in this variable,
libreoffice cannot be built there.
With this patch DEB_VENDOR is always initialized to either Debian or
Ubuntu depending on which the ho
I changed the color from 8bpp to 16bpp, but I don't think it caused the
crash immediately on the next connection, though I don't remember now.
However, once it started crashing, it crashed on every connection
attempt. I changed it to 8bpp and then I could connect without a crash.
I then changed it
@zenigata17 this worked for me, thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tex-common in Ubuntu.
https://bugs.launchpad.net/bugs/1514474
Title:
package tex-common 6.04 failed to install/upgrade: subprocess
installed post
Public bug reported:
while upgrading to 16.04 got this error
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date:
In my case, I had a happy, up-to-date Xenial Ubuntu installation. I
decided to load the xubuntu packages too, as an alternative desktop.
Switching back to regular Ubuntu later, gnome-terminal no longer works,
for the above reasons.
Having determined that the problem is that DBus isn't providing co
I resolved this by disabling the dnsmasq plugin in
/etc/NetworkManager/NetworkManager.conf, as I wanted to keep my own
dnsmasq configuration.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
I can confirm this appears to have resolved the issue for me.
--
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/1283793
Title:
Keyboard doesn't respond during login and in unity without re-
Cool thanks! Btw it's Jon not Joe ;-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1598492
Title:
disable MERGELIBS on ubuntuBSD
Status in libreoffice package in Ubuntu:
Public bug reported:
MERGELIBS is a problem for ubuntuBSD because it triggers very long
command-lines during build which surpass the FreeBSD value for ARG_MAX
(see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208154).
Other GNU/kFreeBSD systems like Debian only enable MERGELIBS for
!kfreebsd
rt-stop-daemon to fix
> this? (note: the debian lightdm package already does this)
>
> This change is needed for ubuntuBSD (which uses SysV init to manage
> system daemons).
>
> Thank you!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.n
Public bug reported:
Hi
Symbols files need some updates in order to build on ubuntuBSD. Please
can you include them?
https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-20160601072740-fr30k90py99vinto/ilmbase.diff-20160426081048-uj0038tten98r2t3-24
Hi
I've updated the patch to 11.2.0-1ubuntu2 as it needed a resync:
https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-20160521075150-b99t0kkt6lhzepsv/mesa.diff-20160426081048-uj0038tten98r2t3-45/mesa.diff
Please could you apply it?
** Patch re
Opened a bug against Ubuntu Gnome for this issue.
https://bugs.launchpad.net/ubuntu-gnome/+bug/1584280
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1562002
Title:
Nautilus: lag af
Unity status is unknown, I only have Ubuntu Gnome installed.
This applies to any action in the menu, "Invert selection" "New Tab" and
any other I tested.
This is causing the whole desktop to hang. I opened the system monitor
to see if it was causing the processor to hang, upon using an item from
re's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch
> which makes cups build fail on ubuntuBSD.
>
> Please could you apply patch below to fix this?
>
> https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
>
> xenial/download/jon%40ubuntubsd.org-2
Hi
The patch needed an update as it didn't apply anymore. Here is it:
https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-20160515013335-qkfnehk373pa1azi/xorgserver.diff-20160426081048-uj0038tten98r2t3-72
/xorg-server.diff
** Patch removed:
Public bug reported:
Hi
There's a small mistake in ubuntu-cupsd-idleexittimeout-upstart.patch
which makes cups build fail on ubuntuBSD.
Please could you apply patch below to fix this?
https://bazaar.launchpad.net/~ubuntubsd/ubuntubsd/patches-
xenial/download/jon%40ubuntubsd.org-201605140
Actually there's some trouble with qxl on ubuntuBSD, see:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568104
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819822
** Bug watch added: Debian Bug tracker #819822
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819822
** Tag
1 - 100 of 275 matches
Mail list logo