Public bug reported:
Gnome Maps simply will no longer start on Ubuntu 20.04.2. Appears to be
a javascript problem.
Output error:
js-Message: 09:44:28.056: JS WARNING:
[resource:///org/gnome/Maps/js/mapSource.js 128]: reference to undefined
property "aerial"
(org.gnome.Maps:10589): Gjs-WARNING
** Description changed:
My Epson WF-2670 Network printer is having issues printing correctly on
Ubuntu. It prints differently depending on what protocol i use, and what
configuration i use. The only configuration that gets it right, is the
Driverless IPP printing on Ubuntu 18.04. However
Public bug reported:
My Epson WF-2670 Network printer is having issues printing correctly on
Ubuntu. It prints differently depending on what protocol i use, and what
configuration i use. The only configuration that gets it right, is the
Driverless IPP printing on Ubuntu 18.04. However using the
I have this bug on Ubuntu, Xubuntu, and Linux Mint. It started only
after installing the recent 14.04 .1 updates. This Bug Effects My
ASUS X54C, But dose not Effect My Dell Latitude E6410.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have linked up this bug (and xkeyboard-config), as I think they are
related:
https://bugs.freedesktop.org/show_bug.cgi?id=45008
I have fixed this by taking two packages from Saucy and installing them
on the affected machines:
xkb-data_2.5.1-3ubuntu2_all.deb
Public bug reported:
Description:Ubuntu 12.04.4 LTS
Release:12.04
byobu:
Installed: 5.17-0ubuntu1
Shift + F12 key combination doesn't work.
Normally in byobu Shift + F12 disables a specific setting, but it
doesn't in 12.04
Also in a custom 4gl (Empress) application we have Shift
Exactly the same here, it's reproducible by me. Using Jaunty with
Amarok 2.0.2 (which uses KDE 4.2.2). I've tried reinstalling everything
to do with amarok that I can find (including the various xine libs)
reinstalling amarok. I've not tried to reinstall KDE as that seems a
bit extreme. It
The backports modules fixed WPA2 personal for me (Wifi link 5100,
jaunty), but I recently tried connecting to a WPA personal AP which
failed. The new module in backports may still not fix WPA personal.
--
[iwlagn] networkmanager applet cannot connect to WPA2 home network (intel 4965)
It is possible/likely this bug is a dup of
https://bugs.launchpad.net/bugs/348275 . The fix described there is to
install linux-backports-modules-jaunty-generic from backports, it has a
new iwlagn module which fixed WPA2 auth for me and at least a few others
so far.
--
[jaunty] Intel WiFi Link
I have to retract that part about a workaround (11n_disable module
option), after a reboot it is back to not working again.
--
[jaunty] Intel WiFi Link 5100/iwlagn not working
https://bugs.launchpad.net/bugs/350370
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm using jaunty release, fresh install, with an Intel Wifi Link 5100
card (Asus N50Vn notebook) and linux-backports-modules-jaunty-generic
fixed WPA2 auth for me. Thanks.
--
[iwlagn] networkmanager applet cannot connect to WPA2 home network (intel 4965)
https://bugs.launchpad.net/bugs/348275
Same or similar issue on an Asus N50Vn (WiFi link 5100) with a fresh
install of jaunty release and a WPA2 personal network. I would get one
green light in NetworkManager for a long time, and then NM would ask
for my password again. Looking at kern.log it appeared as if the
authentication nearly
Confirmed, still present in gutsy. The same fix as in the description
worked for me.
--
en-dv (Dvorak) keymap missing in rdesktop package
https://bugs.launchpad.net/bugs/42616
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Hi Dan, anything additional to report? I should've mentioned that one
thing I intended to do was to get somebody from X.org involved, since
this seems like it must be something upstream of Ubuntu proper.
--
Corrupt screen when switching resolution
https://bugs.launchpad.net/bugs/84158
You
Sigh. I have been meaning to devote more time to this.
I'd be happy to have some help ... frankly if you want to reassign it to
yourself (or if I need to do it) that would be fine. I built and ran
with the version of the radeon module that shipped in Edgy and was able
to reproduce the
I'm doing some digging into this issue.
The capplet isn't the problem, it merely retrieves and sets resolutions
via the RandR X extension. I can create the same corruption by using
xrandr(1) to switch to the problematic display modes.
Interestingly corruption happens only in display modes
: (unassigned) = Matthew Moore
--
Corrupt screen when switching resolution
https://bugs.launchpad.net/bugs/84158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
I have encountered this same issue with my Asus M6Ne laptop, with an ATI
Mobility Radeon 9700, in Feisty Release.
The autogenerated xorg.conf did not include resolutions higher than
1024x768. Switching to any resolutions higher than 1024x768 in the
capplet resulted in the same type of corruption
my lspci -v output
** Attachment added: lspci.txt
http://librarian.launchpad.net/7483099/lspci.txt
--
Corrupt screen when switching resolution
https://bugs.launchpad.net/bugs/84158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Unconfirmed = Confirmed
--
Corrupt screen when switching resolution
https://bugs.launchpad.net/bugs/84158
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
20 matches
Mail list logo
