[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04

2022-03-31 Thread Jason Haar
Well funny you should say that... When I installed 22.04 on my new Dell
laptop with 16G RAM, Jammy still only allocated 976MB of swap. I think
you have a problem there too.

So after reporting this issue and continually having OOM crashes, I
created a 20G swapfile - and ever since this problem has disappeared...

Maybe running with such a starved swapspace triggers systemd-oom to do
weird things?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966381

Title:
  applications crash that never crashed under Ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04

2022-03-28 Thread Jason Haar
Oh well, that latest systemd-oom didn't help. Chrome just crashed again
- while I wasn't even using the computer. Here are all the syslogs at
the time it crashed - nothing but the OOM

Mar 28 19:30:56 ubuntu systemd-oomd[1121]: Killed 
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-google\x2dchrome-5640.scope
 due to memory used (15992975360) / total (16153948160) and swap used 
(921436160) / total (1023406080) being more than 90.00%
Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: 
systemd-oomd killed 311 process(es) in this unit.
Mar 28 19:30:56 ubuntu systemd[5083]: app-gnome-google\x2dchrome-5640.scope: 
Consumed 7h 10min 56.132s CPU time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966381

Title:
  applications crash that never crashed under Ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966603] [NEW] gnome shell add-on in FF broke with forced move to snap version

2022-03-27 Thread Jason Haar
Public bug reported:

Looks like the FF add-on that allows you to review/alter gnome-shell
extensions no longer works now that firefox is a snap. It was working
when I initially installed Ubuntu-22.04 two weeks ago (I chose native
apt of FF over snap then), but last week there was the announcement-and-
forced-move over to a snap - I would guess that's when it broke.

I just now removed the add-on from within FF, restarted FF, added it
back in - and it still doesn't work. I have a bunch of FF add-ons (like
uBlock Origin) and I think they are working - so this seems fairly
specific to "Gnome Shell Extension"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 07:39:22 2022
InstallationDate: Installed on 2022-03-13 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
Snap.Changes: no changes found
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966603

Title:
  gnome shell add-on in FF broke with forced move to snap version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966603/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966602] [NEW] Screen not locked after inactivity

2022-03-27 Thread Jason Haar
Public bug reported:

I did a fresh install of Ubuntu-22.04 two weeks ago. I don't think the
automatic lock on idle feature has worked the entire time (and I've been
patching all the time when available). If I manually lock the screen it
works - but if I don't, I can go to bed and the next day it's still
unlocked. syslog doesn't show any obvious gnome-screensaver error, so I
wonder if this is actually a Wayland issue - ie it isn't telling gnome-
screensaver about inactivity triggers? I dunno - just guessing.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-screensaver 3.6.1-13ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 07:06:47 2022
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 900
 org.gnome.desktop.session session-name 'ubuntu'
InstallationDate: Installed on 2022-03-13 (13 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen not locked after inactivity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966602

Title:
  Screen not locked after inactivity

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1966602/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966381] Re: applications crash that never crashed under Ubuntu-20.04

2022-03-25 Thread Jason Haar
FYI About 6 hours ago I saw a new release of systemd-oom was released
(249.11-0ubuntu2). I've upgraded the entire system and rebooted, so I'll
report back if there's any change. I was getting these random OOM about
every couple of days, so within a week should know if that changed
anything

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966381

Title:
  applications crash that never crashed under Ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966381] [NEW] applications crash that never crashed under Ubuntu-20.04

2022-03-25 Thread Jason Haar
Public bug reported:

Just now I was watching some video in Firefox. I popped over to another
virtual workspace for a few minutes, and when I popped back to Firefox
it had gone. The same thing had been happening all week (I installed
fresh Ubuntu-22.04 last week) with Chrome, Firefox and Thunderbird.

This time instead of shrugging it off I looked in the logs, and found
this

Mar 25 19:45:40 ubuntu systemd-oomd[960]: Killed 
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-firefox-6607.scope
 due to memory used (15940579328) / total (16153944064) and swap used 
(925564928) / total (1023406080) being more than 90.00%
Mar 22 08:11:29 ubuntu systemd[5029]: app-gnome-google\x2dchrome-5412.scope: 
systemd-oomd killed 298 process(es) in this unit.
Mar 23 11:09:28 ubuntu systemd-oomd[1055]: Killed 
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-thunderbird-5418.scope
 due to memory used (15591993344) / total (16149745664) and swap used 
(927760384) / total (1023406080) being more than 90.00%
Mar 23 11:09:28 ubuntu systemd[5029]: app-gnome-thunderbird-5418.scope: 
systemd-oomd killed 173 process(es) in this unit.

I know it's saying those three entirely unrelated applications had
suddenly decided to swallow all the RAM+swap on this laptop of mine -
but the very same apps didn't act like that last week under
Ubuntu-20.04, so I suspect something else is going on

I can't say they hadn't swallowed all the RAM, but there is ZERO sign of
a system on the verge of collapsing - everything has been screaming
along just nicely - no sign of the "staggering" you normally get when
the OS is heavily into swap.

However, now that I look I see my 16G laptop only has 1G swap??? I just
let the Ubuntu installer do it's defaults - but it used to auto-choose
1xRAM or 2xRAM - what's with this 1G swap? Could that be related?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: systemd-oomd 249.11-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 25 19:47:44 2022
InstallationDate: Installed on 2022-03-13 (11 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966381

Title:
  applications crash that never crashed under Ubuntu-20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1966037] [NEW] some applications hang for up to 30sec due to /run/systemd/resolve/io.systemd.Resolve

2022-03-23 Thread Jason Haar
Public bug reported:

I just installed Ubuntu-22.04 last week and have noticed lots of command
line apps seem to hang for 10-30sec before working. Eventually that got
annoying enough that I looked into it.

Anyway, apps like "telnet" (yep, I'm that old) and oddly enough sudo
showed this issue strongly. In the end I ran them with strace and could
see the pause occurred when  /run/systemd/resolve/io.systemd.Resolve was
called. So systemd-resolve was involved.

Then I cranked up "tcpdump -n -i any port 53" and re-ran the commands.
What I found was systemd-resolver was throwing DNS lookups for my
hostname at all the DNS servers I had configured (default on wifi plus
corporate always-on VPN link). Now the thing is our corporate VPN has
SIXTEEN domains in the search domain field... So as systemd-resolver was
doing one "A" plus one "" lookups for each "hostname.search-domain"
- well there's the hang. In fact 30sec is quite a good response time ;-)

To fix it I simply added my raw (ie non-dot) hostname to /etc/hosts -
completely blocked this self-hostname lookup that must be going on. Now
there are no DNS lookups at all for my hostname in this situation.

All is good. But it does make me wonder if perhaps Ubuntu shouldn't
always put the hostname into /etc/hosts? Even pointing at 127.0.0.99
(for example) might be enough (I haven't actually tested that - I'm
pointing it at my static VPN IP)

Anyway, this is a corner case for sure - but it might shave some delays
off a bunch of folks. This also might seem cosmetic, but I would guess
any application that calls gethostbyname or equivalent on itself is
triggering this.

PS: I had Ubuntu-20.04 before this and didn't have the problem. But
looking at a backup I can see I also had my hostname in the /etc/hosts
file - so this might have affected 20.04 too but I "accidentally" fixed
it early on without realizing it

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966037

Title:
  some applications hang for up to 30sec due to
  /run/systemd/resolve/io.systemd.Resolve

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966037/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965214] Re: keep getting asked to set a Primary Password?

2022-03-16 Thread Jason Haar
Sigh. Please close ticket. After hitting Send I went and looked at
Preferences again and NOW I see there's a Security section where you can
turn off the Primary Password feature.

Sorry for wasting your time. :-/

Jason

** Changed in: remmina (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965214

Title:
  keep getting asked to set a Primary Password?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965214] [NEW] keep getting asked to set a Primary Password?

2022-03-16 Thread Jason Haar
Public bug reported:

Under Ubuntu-22.04beta I am continually getting prompted to set what I
assume is a master password for remmina cred changes. The issue is that
I have it configured to save to gnome-keyring. And if I bring up that
gnome-keyring I can see the remmina creds I've saved in there - so all
is good on that front.

ie the gnome-keyring and whatever this "primary password" thing is are
doing the same thing and only one should win - the latter should be
disabled. There doesn't seem to be any way to disable it - I am just
hitting cancel and it keeps popping up later.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: remmina 1.4.24+dfsg-2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 17 16:06:00 2022
InstallationDate: Installed on 2022-03-13 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: remmina
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: remmina (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965214

Title:
  keep getting asked to set a Primary Password?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965214/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965088] [NEW] mouse selects creates solid white blocks in remmina?

2022-03-16 Thread Jason Haar
Public bug reported:

I've used remmina for years and normally don't fiddle with defaults
much. I've moved from Ubuntu-20.04 to 22.04beta and I've noticed that my
Linux SSH sessions now have weird mouse behaviour. If I use the mouse to
"Select" content, instead of the traditional "transparent" format
occurring, I see a solid white area. eg if I selected a screenful of
content in gnome-terminal, the default purple background with white text
becomes white background with black text. But in remmina, the black
background with white text becomes white background with white text - ie
it's all white.


Just to reiterate, if I do the same action in gnome-terminal or firefox/etc it 
is "normal" - this seems to be remmina-specific

Any ideas how to fix this?

Thanks

Jason

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: remmina 1.4.24+dfsg-2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 16 19:30:50 2022
InstallationDate: Installed on 2022-03-13 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: remmina
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: remmina (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965088

Title:
  mouse selects creates solid white blocks in remmina?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1965088/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1801495] [NEW] cannot resolve Active Directory realm name with large number of A records

2018-11-03 Thread Jason Haar
Public bug reported:

We have 3 Active Directory "realms". One has 25 domain controllers/DNS
servers and the other two both have 35+. The way that AD works means
this creates DNS 'A' records for the realm name that resolves to all the
Domain Controllers/DNS servers that service it (ie a DNS name with many
A records).

If we have a fully patched/updated Ubuntu-18.04.1 system, running
"nslookup small.realm.name" returns the 25 DNS servers, and life is
good. Running "nslookup large.realm.name" works - but only returns 30
DNS servers (out of 35+). Running the same command on a CentOS-6 system
(ie no systemd) returns 35+ DNS servers. So that's a (minor) bug?

...but ping and other real applications are the real problem  - they
don't work at all in the larger realms. "ping small.realm.name" works
fine, but "ping large.realm.name" returns "Temporary failure in name
resolution". Also telnet, etc doesn't work. "ping
servername.large.realm.name" works fine - just the domain name itself
doesn't work - which makes me think it's related to the number of A
records being returned.

We are trying to add these Ubuntu laptops to our AD domains - which
requires several calls to "large.realm.name" - which is failing -  but
so far can only get it to work in small.realm.name due to this issue.  I
think this is a systemd-resolved bug? (237-3ubuntu10.3)

Thanks

Jason

** Affects: trace-summary (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: systemd-resolved

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801495

Title:
  cannot resolve Active Directory realm name with large number of A
  records

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trace-summary/+bug/1801495/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1371783] Re: package ttf-mscorefonts-installer 3.4+nmu1ubuntu2 (utopic) fails to install/upgrade

2016-04-08 Thread Jason Haar
It's also happening for Ubuntu-16.04. Wow - two years

I'm not even sure what the fonts are for - I've removed the corrupt
package and will see if I can live without it

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371783

Title:
  package ttf-mscorefonts-installer 3.4+nmu1ubuntu2 (utopic) fails to
  install/upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/msttcorefonts/+bug/1371783/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-08-04 Thread Jason Haar
I think the problem has re-appeared :-(

I rebooted 16 days ago and can see that 18 days ago (2014-07-18) there
was a compiz update

compiz-core:amd64 (0.9.11.1+14.04.20140701-0ubuntu1,
0.9.11.2+14.04.20140714-0ubuntu1) [plus related]

What I've noticed in the past week is that windows are starting to show
up where they aren't meant to be. ie it's "collapsing" in on itself
again, exactly the same as my bug report in 1321221 (ie going from
laptop to docking station-with-monitor and visa/versa triggers it)

Could the patch have been reversed out?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1304531/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1346118] Re: Printers app doesn't seem to do dns-sd

2014-07-21 Thread Jason Haar
I just added a PTR record for _services._dns-sd._udp.our.domain
referring to our _ipp._tcp. record and that made a difference

Now avahi-discover immediately allows me to click my way down the the
print queue under "Internet Printer", so that made avahi happy

I then restarted cups/cups-browsed and then ran system-config-printer,
but still the printer doesn't magically show up, either on the opening
screen, nor the "Add" screen (I would have expected "discovered"
printers to show up there?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346118

Title:
  Printers app doesn't seem to do dns-sd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1346118] Re: Printers app doesn't seem to do dns-sd

2014-07-21 Thread Jason Haar
** Attachment added: "avahi-daemon.conf"
   
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+attachment/4159703/+files/avahi-daemon.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346118

Title:
  Printers app doesn't seem to do dns-sd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1346118] Re: Printers app doesn't seem to do dns-sd

2014-07-21 Thread Jason Haar
The CUPS server is a CentOS-6 box. I should have mentioned I can
explicitly add the queue manually - it's only the "automagic" method of
dns-sd that doesn't work

ie on the Ubuntu laptop

"Printers->Add->ipp://cups.server.name/printers/queueName"

works just fine, the queue is added and I can print to it

* cups-browsed is running
* avahi-daemon is running on the laptop and is not needed on the server. I am 
WAN connected to the server, so broadcast/multicast methods are never going to 
work - that's the entire point of me trying dns-sd :-). Instead we have 
manually installed dns-sd related DNS records pointing to the CUPS server
* avahi-discover wasn't installed on the laptop. After I installed it (also 
installed avahi-discover as a dependency), running it produced a GUI containing 
lots of local broadcast-based stuff (eg iphones, vnc, ssh; both ipv4/ipv6). 
Right at the bottom was "WAN", opening that showed our corporate DNS domain, 
but double-clicking on it didn't do anything - nor did a sniffer show any 
dns-sd* lookups. There is no "Internet Printer" nor "ipp*" section 

I have winbind installed (the Ubuntu laptop is AD integrated) and can
see it doing Active-Directory related DNS SRV lookups, so DNS is
definitely working, and if I manually lookup records like

dig ptr b._dns-sd._udp.our.domain

...then I get directed appropriately, and following the chain down the
rabbit hole I end up with the appropriate TXT and SRV records needed to
use that IPP queue. But as the laptop doesn't do the initial dns-sd
lookups, that cannot happen

The /etc/cups/cups-browsed.conf file has CreateIPPPrinterQueues
commented out, I uncommented that and restarted cupsd/cups-browsed and
saw some DNS lookups for  _services._dns-sd._udp.our.domain - but we
don't have any records in there (and Macs don't seem to use that)


** Attachment added: "cups-browsed.conf"
   
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+attachment/4159702/+files/cups-browsed.conf

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346118

Title:
  Printers app doesn't seem to do dns-sd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1346118] [NEW] Printers app doesn't seem to do dns-sd

2014-07-21 Thread Jason Haar
Public bug reported:

I've just spent some time reconfiguring our DNS so that Macs could
discover our CUPS print queues using dns-sd/bonjour

I was surprised when I discovered this Ubuntu 14.04 laptop couldn't do
the same thing. I have got a sniffer up watch all DNS traffic, and yet
when I enter the "Printers" app to Add a printer, it shows no evidence
of hanging whilst doing a scan, and certainly shows no DNS lookups for
the standard PTR/SRV/TXT records used in dns-sd

Is this supported by Ubuntu? I used to use Fedora and vaguely feel this
worked in Gnome3?

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: system-config-printer-gnome 1.4.3+20140219-0ubuntu2.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CupsErrorLog:
 E [21/Jul/2014:11:36:09 +1200] [Client 25] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost/printers/Generic-text-only) from localhost
 E [21/Jul/2014:11:42:31 +1200] [Job 13] Aborting job because it has no files.
 E [21/Jul/2014:12:02:08 +1200] [Client 26] Returning IPP 
client-error-bad-request for Create-Job (ipp://localhost:631/printers/MFC7340) 
from localhost
 E [21/Jul/2014:20:55:27 +1200] [Client 17] pam_authenticate() returned 7 
(Authentication failure)
 E [21/Jul/2014:20:55:31 +1200] [Client 17] pam_authenticate() returned 7 
(Authentication failure)
CurrentDesktop: Unity
Date: Mon Jul 21 21:12:08 2014
InstallationDate: Installed on 2014-05-01 (80 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lpstat:
 device for Cups-Email: ipp://192.168.248.3:631/printers/Cups-Email
 device for Cups-PDF: ipp://whanau.org:631/printers/Cups-Email
 device for MFC7340: ipp://192.168.248.3:631/printers/MFC7340
 device for PRN-L1-IS-BW: ipps://crom.ap.trimblecorp.net/printers/PRN-L1-IS-BW
MachineType: Dell Inc. Latitude E7440
PackageArchitecture: all
Papersize: a4
PpdFiles: PRN-L1-IS-BW: Generic PostScript Printer Foomatic/Postscript 
(recommended)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: system-config-printer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 03HFCG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346118

Title:
  Printers app doesn't seem to do dns-sd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1346118/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1337997] [NEW] twinkle no longer a GUI app???

2014-07-04 Thread Jason Haar
Public bug reported:

I'm a long time twinkle user under Fedora, who has just moved to Ubuntu
with 14.04

Anyway, it simply doesn't work. If I have no $HOME/.twinkle directory,
and run it from a shell, it gives errors about there being no config and
hangs. If I touch the $HOME/.twinkle/twinkle.cfg file, then seems to be
defaulting to some autodiscover mode - writing debugging to STDOUT - but
no GUI shows up

Running "ldd /usr/bin/twinkle" doesn't show any X-windows/QT related
libraries I'd expect. I suspect this is simply totally broken?

BTW, I originally had my Fedora $HOME/.twinkle/ directory (with my SIP
accounts/etc). twinkle gives no errors but again no GUI shows up

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: twinkle 1:1.4.2-4
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul  5 11:27:25 2014
InstallationDate: Installed on 2014-05-01 (64 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: twinkle
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: twinkle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337997

Title:
  twinkle no longer a GUI app???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1337997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-07-01 Thread Jason Haar
I haven't had the problem since I upgraded, so I've marked it as
"Confirmed". Hopefully that was the right thing to do

** Changed in: compiz (Ubuntu Trusty)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1304531/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-06-26 Thread Jason Haar
Thanks for that, I have done that now and have the newer version, let's
see how it goes :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1304531/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-06-25 Thread Jason Haar
Hi there

I implemented the patch some weeks ago and had great success. But
yesterday and today the problem came back! In both cases going from work
with a laptop docked into an external monitor to home with no external
monitor triggered the collapse of some of my apps in separate workspaces
back into one workspace

I'm a long time Fedora user but a first-time Ubuntu user, so my log
searches may be off, but I don't think my patched compiz has been
replaced with an more-official-but-broken version (dated May 20,
compiz-1:0.9.11+14.04.20140423-0ub), so it looks like the patched
version may still have a glitch in it. Pity  - it has worked rock-solid
since it was installed until yesterday

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1304531/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1329511] [NEW] dhcp lease renewal treated as equivalent to ifup?

2014-06-12 Thread Jason Haar
Public bug reported:

I routinely sit on our work guest network which has a 1 hour DHCP lease
time.

What I'm noticing is that every hour skype and pidgin are reporting
"buddy offline,.,buddy online". What appears to be happening is the
NetworkManager is (successfully) renewing the lease - but appears to
trigger whatever APIs it normally triggers when network changes occur.
In other words, renewing a DHCP lease seems to be treated the same as
resetting a network interface

I don't know if this is a bug or is expected behaviour, but from a user
perspective I do not understand why successfully checking if the IP
address you have is still valid should trigger anything: nothing has
changed, so why "tell" other applications that something has? To put it
another way, if I set a static IP, I bet these applications would no
longer think network changes are occurring, so why can't the same thing
happen with successful DHCP renewals

Thanks for listening

Jason

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Fri Jun 13 08:47:36 2014
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-05-01 (42 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_NZ:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
ftp_proxy: http://localhost:3128/
http_proxy: http://localhost:3128/
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-05-02T16:40:21.190732
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 98:D6:F7:D1:30:7B bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/7  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled
no_proxy: trimblecorp.net

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329511

Title:
  dhcp lease renewal treated as equivalent to ifup?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1329511/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1321221] Re: apps in different workspaces are collapsing into a smaller number of workspaces

2014-05-23 Thread Jason Haar
It's been 3 days now, and all problems are solved!

I have slept/unslept the laptop going to/from work, plugged it into/out
of docking station (ie flipping between laptop display and external
monitor) - all without the symptom of collapsing workspaces occurring

I think you've fixed it!

Thanks :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321221

Title:
  apps in different workspaces are collapsing into a smaller number of
  workspaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1321221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1321221] Re: apps in different workspaces are collapsing into a smaller number of workspaces

2014-05-20 Thread Jason Haar
Done. I've upgraded, and logged out and in again. We'll see how it goes
and I'll let you know in 1-2 days :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321221

Title:
  apps in different workspaces are collapsing into a smaller number of
  workspaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1321221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1321221] Re: apps in different workspaces are collapsing into a smaller number of workspaces

2014-05-20 Thread Jason Haar
1. Yes! As I'm doing the "one app per workspace" thang, I maximize the app
2. it's a latop and I dock it at work (ie external monitor) and undock to take 
home (with no external monitor), but I'm mostly sure this issue happens even 
during one of those periods. eg last night at home I was working away and 
jumped to a window I'd been in before and it was full of other apps. But I do 
agree this is primarily noticed when I am interacting for the first time after 
changing laptop <->docked
3. yes. I sleep it to/from work to home  - which goes hand in hand with the 
docked/laptop transition, so maybe it's nothing to do with external monitors 
and more to do with sleeping (or maybe how sleep affects display renegotiation 
after waking up?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321221

Title:
  apps in different workspaces are collapsing into a smaller number of
  workspaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1321221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1321221] [NEW] apps in different workspaces are collapsing into a smaller number of workspaces

2014-05-20 Thread Jason Haar
Public bug reported:

I have just migrated from Fedora/Gnome3 and am too used to workspaces to
get along with the defaults that unity has :-)

So I have used unity-tweak-tool to give myself 8x1 workspaces, and put
thunderbird in one, firefox in another, etc. What I am finding is
several times PER DAY I suddenly discover that a bunch of apps are now
in the same workspace rather than the separate ones I put them into. I
still have 8 - but most are empty

There is no error, and they (say) go from 5 in use to (say) 3 in use -
not a total collapse and not showing any app dependency. eg I may find
firefox and thunderbird in the same workspace and another time find
remmina sitting underneath some terminal shells

The only extra piece of info is that it appears to only happen to the
workspaces that I'm not currently in. ie I don't see this happening in
the current one - always another one. Sort of Heisenburg's uncertainly
principle at work!

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue May 20 22:04:56 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05cb]
InstallationDate: Installed on 2014-05-01 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Latitude E7440
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 03HFCG
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu May 15 12:24:24 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   41055 
 vendor DEL
xserver.version: 2:1.15.1-0ubuntu2

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321221

Title:
  apps in different workspaces are collapsing into a smaller number of
  workspaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1321221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 387308] Re: HTTPS Proxy Support for file sync

2010-04-25 Thread Jason Haar
I'm trying to bring up 10.04 behind a corporate proxy and it appears
that Ubuntu One is connecting to the proxy - but thinks it's the Ubuntu
One web server instead of a proxy!

i.e. a sniffer shows that instead of seeing

CONNECT https://launchpad.whatever

I see

random stuff that looks like SSL to me

...followed by a SSL error popup under Ubuntu

It is very common for corporate networks to block outbound Web and force
their users through proxies. Ubuntu won't be usable within those
environments with such a fault

Jason

-- 
HTTPS Proxy Support for file sync
https://bugs.launchpad.net/bugs/387308
You received this bug notification because you are a member of Ubuntu
Bugs, which is a subscriber of a duplicate bug.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 445317] Re: netbook-launcher crashed with SIGSEGV in cogl_get_features()

2010-02-27 Thread Jason Haar
I found my problem. I was running it at 16bit colour due to the low-end
card. However, putting it back to 24bit made the crashing disappear. I
now have a working netbook-launcher - but can't use it (10sec for a
click to work isn't acceptable). I'll see if there's some other wm or
something...

-- 
netbook-launcher crashed with SIGSEGV in cogl_get_features()
https://bugs.launchpad.net/bugs/445317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 445317] Re: netbook-launcher crashed with SIGSEGV in cogl_get_features()

2010-02-27 Thread Jason Haar
I can add "me too". I am trying to squeeze a bit more life out of my
sons old PC - it has a nvidia GeForce2 MX/MX 400 with a Viewsonic PS17
CRT monitor. When I installed UNR it correctly installed the proprietary
nvidia drivers, but it couldn't autodetect the old monitor and it came
up in 300-somethingx400something resolution - horrible - but everything
worked. Anyway, after much fiddling I  got it to hardwired to 1024x768
and 16K colours and thought it'd be alright. However, upon first logging
in I got the orange background but no window manager. I Alt-F2 xterm and
could see netbook-launcher taking 90% CPU and dmesg shows all these
errors

[  485.056709] netbook-launche[2602]: segfault at 0 ip 008b5e93 sp bff6e8b0 
error 4 in libclutter-glx-1.0.so.0.0.6[857000+ab000]
[  486.039663] netbook-launche[2604]: segfault at 0 ip 0016ee93 sp bf9c4bd0 
error 4 in libclutter-glx-1.0.so.0.0.6[11+ab000]
[  486.998045] netbook-launche[2606]: segfault at 0 ip 00624e93 sp bf930c70 
error 4 in libclutter-glx-1.0.so.0.0.6[5c6000+ab000]
[  487.936006] netbook-launche[2608]: segfault at 0 ip 00c8fe93 sp bfee6b30 
error 4 in libclutter-glx-1.0.so.0.0.6[c31000+ab000]
[  488.880603] netbook-launche[2610]: segfault at 0 ip 00ebee93 sp bfd1dce0 
error 4 in libclutter-glx-1.0.so.0.0.6[e6+ab000]

-- 
netbook-launcher crashed with SIGSEGV in cogl_get_features()
https://bugs.launchpad.net/bugs/445317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs